Digital processing systems and methods for draft and time slider for presentations in collaborative work systems

ABSTRACT

Systems, methods, and computer-readable media for tracking on a slide-by-slide basis, edits to presentation slides are disclosed. The systems and methods may involve accessing a stored deck of presentation slides; populating a first window, a second window, and a third window with slides of the deck; receiving a selection of a particular slide having a current version displayed in the second window and a former version displayed in the third window; receiving a first selection of the particular slide in the second window; upon receipt of the first selection, causing a rendition of the particular slide to appear in the first window; receiving a second selection of the particular slide in the third window; and upon receipt of the second selection, causing a rendition of the particular slide to appear in the first window.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on and claims benefit of priority ofInternational Patent Application No. PCT/IB2021/062440 filed on Dec. 29,2021, which claims priority to U.S. Provisional Patent Application No.63/233,925, filed Aug. 17, 2021, U.S. Provisional Patent Application No.63/273,448, filed Oct. 29, 2021, U.S. Provisional Patent Application No.63/273,453, filed Oct. 29, 2021, International Patent Application No.PCT/IB2021/000024, filed on Jan. 14, 2021, International PatentApplication No. PCT/IB2021/000090, filed on Feb. 11, 2021, andInternational Patent Application No. PCT/IB2021/000297, filed on Apr.28, 2021, the contents of all of which are incorporated herein byreference in their entireties.

TECHNICAL FIELD

Embodiments consistent with the present disclosure include systems andmethods for collaborative work systems. The disclosed systems andmethods may be implemented using a combination of conventional hardwareand software as well as specialized hardware and software, such as amachine constructed and/or programmed specifically for performingfunctions associated with the disclosed method steps. Consistent withother disclosed embodiments, non-transitory computer-readable storagemedia may store program instructions, which may be executable by atleast one processing device and perform any of the steps and/or methodsdescribed herein.

BACKGROUND

Operation of modern enterprises can be complicated and time consuming.In many cases, managing the operation of a single project requiresintegration of several employees, departments, and other resources ofthe entity. To manage the challenging operation, project managementsoftware applications may be used. Such software applications allow auser to organize, plan, and manage resources by providingproject-related information in order to optimize the time and resourcesspent on each project. It would be useful to improve these softwareapplications to increase operation management efficiency.

SUMMARY

One aspect of the present disclosure may be directed to systems,methods, and computer readable media for tracking on a slide-by-slidebasis, edits to presentation slides. Systems, methods, devices, andnon-transitory computer readable mediums may include at least oneprocessor that is configured to: present a first window defining a slidepane for displaying a slide subject to editing; present in a secondwindow a current graphical slide sequence pane, for graphicallydisplaying a current sequence of slides in the deck; present in a thirdwindow an historical graphical slide sequence pane for graphicallypresenting a former sequence of slides in the deck; access a stored deckof presentation slides; populate the first window, the second window,and the third window with slides of the deck; receive a selection of aparticular slide having a current version displayed in the second windowand a former version displayed in the third window; receiving a firstselection of the particular slide in the second window; upon receipt ofthe first selection, cause a rendition of the particular slide to appearin the first window; receive a second selection of the particular slidein the third window; and upon receipt of the second selection, cause arendition of the particular slide to appear in the first window.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary computing device which may beemployed in connection with embodiments of the present disclosure.

FIG. 2 is a block diagram of an exemplary computing architecture forcollaborative work systems, consistent with embodiments of the presentdisclosure.

FIG. 3 illustrates an example of an electronic collaborative wordprocessing document, consistent with some embodiments of the presentdisclosure.

FIG. 4 illustrates an example of a collaborative electronic document,consistent with some embodiments of the present disclosure.

FIG. 5A illustrates an example of a first instance of a collaborativeelectronic document, consistent with some embodiments of the presentdisclosure.

FIG. 5B illustrates an example of a second instance of a collaborativeelectronic document, consistent with some embodiments of the presentdisclosure.

FIG. 6 illustrates an example of a duplicate version of a collaborativeelectronic document, consistent with some embodiments of the presentdisclosure.

FIG. 7 illustrates a block diagram of an exemplary process for enablingsimultaneous group editing of electronically stored documents,consistent with some embodiments of the present disclosure.

FIG. 8 illustrates an example of a first instance of an electronicdocument, consistent with some embodiments of the present disclosure.

FIG. 9 illustrates an example of a second instance of an electronicdocument, consistent with some embodiments of the present disclosure.

FIG. 10A illustrates an example of a third instance of an electronicdocument, consistent with some embodiments of the present disclosure.

FIG. 10B illustrates an example of a fourth instance of an electronicdocument, consistent with some embodiments of the present disclosure.

FIG. 10C illustrates an example of a fifth instance of an electronicdocument, consistent with some embodiments of the present disclosure.

FIG. 11 illustrates an example of a rolled-back display reflecting editsmade to a specific portion of an electronic document, consistent withsome embodiments of the present disclosure.

FIG. 12 illustrates a block diagram of an exemplary process for enablinggranular rollback of historical edits in an electronic document,consistent with some embodiments of the present disclosure.

FIG. 13A illustrates an example of a first instance of a stored deck ofpresentation slides, consistent with some embodiments of the presentdisclosure.

FIG. 13B illustrates an example of a second instance of a stored deck ofpresentation slides, consistent with some embodiments of the presentdisclosure.

FIG. 13C illustrates an example of a third instance of a stored deck ofpresentation slides, consistent with some embodiments of the presentdisclosure.

FIG. 14 illustrates an example of a timeline slider, consistent withsome embodiments of the present disclosure.

FIG. 15 illustrates a block diagram of an exemplary process for trackingon a slide-by-slide basis, edits to presentation slides, consistent withsome embodiments of the present disclosure.

DETAILED DESCRIPTION

Exemplary embodiments are described with reference to the accompanyingdrawings. The figures are not necessarily drawn to scale. While examplesand features of disclosed principles are described herein,modifications, adaptations, and other implementations are possiblewithout departing from the spirit and scope of the disclosedembodiments. Also, the words “comprising,” “having,” “containing,” and“including,” and other similar forms are intended to be equivalent inmeaning and be open ended in that an item or items following any one ofthese words is not meant to be an exhaustive listing of such item oritems, or meant to be limited to only the listed item or items. Itshould also be noted that as used herein and in the appended claims, thesingular forms “a,” “an.” and “the” include plural references unless thecontext clearly dictates otherwise.

In the following description, various working examples are provided forillustrative purposes. However, is to be understood the presentdisclosure may be practiced without one or more of these details.

Throughout, this disclosure mentions “disclosed embodiments,” whichrefer to examples of inventive ideas, concepts, and/or manifestationsdescribed herein. Many related and unrelated embodiments are describedthroughout this disclosure. The fact that some “disclosed embodiments”are described as exhibiting a feature or characteristic does not meanthat other disclosed embodiments necessarily share that feature orcharacteristic.

This disclosure presents various mechanisms for collaborative worksystems. Such systems may involve software that enables multiple usersto work collaboratively. By way of one example, workflow managementsoftware may enable various members of a team to cooperate via a commononline platform. It is intended that one or more aspects of anymechanism may be combined with one or more aspect of any othermechanisms, and such combinations are within the scope of thisdisclosure.

This disclosure is constructed to provide a basic understanding of a fewexemplary embodiments with the understanding that features of theexemplary embodiments may be combined with other disclosed features ormay be incorporated into platforms or embodiments not described hereinwhile still remaining within the scope of this disclosure. Forconvenience, and form of the word “embodiment” as used herein isintended to refer to a single embodiment or multiple embodiments of thedisclosure.

Certain embodiments disclosed herein include devices, systems, andmethods for collaborative work systems that may allow a user to interactwith information in real time. To avoid repetition, the functionality ofsome embodiments is described herein solely in connection with aprocessor or at least one processor. It is to be understood that suchexemplary descriptions of functionality applies equally to methods andcomputer readable media and constitutes a written description ofsystems, methods, and computer readable media. The underlying platformmay allow a user to structure a systems, methods, or computer readablemedia in many ways using common building blocks, thereby permittingflexibility in constructing a product that suits desired needs. This maybe accomplished through the use of boards. A board may be a tableconfigured to contain items (e.g., individual items presented inhorizontal rows) defining objects or entities that are managed in theplatform (task, project, client, deal, etc.). Unless expressly notedotherwise, the terms “board” and “table” may be considered synonymousfor purposes of this disclosure. In some embodiments, a board maycontain information beyond which is displayed in a table. Boards mayinclude sub-boards that may have a separate structure from a board.Sub-boards may be tables with sub-items that may be related to the itemsof a board. Columns intersecting with rows of items may together definecells in which data associated with each item may be maintained. Eachcolumn may have a heading or label defining an associated data type.When used herein in combination with a column, a row may be presentedhorizontally and a column vertically. However, in the broader genericsense as used herein, the term “row” may refer to one or more of ahorizontal and/or a vertical presentation. A table or tablature as usedherein, refers to data presented in horizontal and vertical rows, (e.g.,horizontal rows and vertical columns) defining cells in which data ispresented. Tablature may refer to any structure for presenting data inan organized manner, as previously discussed, such as cells presented inhorizontal rows and vertical columns, vertical rows and horizontalcolumns, a tree data structure, a web chart, or any other structuredrepresentation, as explained throughout this disclosure. A cell mayrefer to a unit of information contained in the tablature defined by thestructure of the tablature. For example, a cell may be defined as anintersection between a horizontal row with a vertical column in atablature having rows and columns. A cell may also be defined as anintersection between a horizontal and a vertical row, or as anintersection between a horizontal and a vertical column. As a furtherexample, a cell may be defined as a node on a web chart or a node on atree data structure. As would be appreciated by a skilled artisan,however, the disclosed embodiments are not limited to any specificstructure, but rather may be practiced in conjunction with any desiredorganizational arrangement. In addition, tablature may include any typeof information, depending on intended use. When used in conjunction witha workflow management application, the tablature may include anyinformation associated with one or more tasks, such as one or morestatus values, projects, countries, persons, teams, progress statuses, acombination thereof, or any other information related to a task.

While a table view may be one way to present and manage the datacontained on a board, a table's or board's data may be presented indifferent ways. For example, in some embodiments, dashboards may beutilized to present or summarize data derived from one or more boards. Adashboard may be a non-table form of presenting data, using, forexample, static or dynamic graphical representations. A dashboard mayalso include multiple non-table forms of presenting data. As discussedlater in greater detail, such representations may include various formsof graphs or graphics. In some instances, dashboards (which may also bereferred to more generically as “widgets”) may include tablature.Software links may interconnect one or more boards with one or moredashboards thereby enabling the dashboards to reflect data presented onthe boards. This may allow, for example, data from multiple boards to bedisplayed and/or managed from a common location. These widgets mayprovide visualizations that allow a user to update data derived from oneor more boards.

Boards (or the data associated with boards) may be stored in a localmemory on a user device or may be stored in a local network repository.Boards may also be stored in a remote repository and may be accessedthrough a network. In some instances, permissions may be set to limitboard access to the board's “owner” while in other embodiments a user'sboard may be accessed by other users through any of the networksdescribed in this disclosure. When one user makes a change in a board,that change may be updated to the board stored in a memory or repositoryand may be pushed to the other user devices that access that same board.These changes may be made to cells, items, columns, boards, dashboardviews, logical rules, or any other data associated with the boards.Similarly, when cells are tied together or are mirrored across multipleboards, a change in one board may cause a cascading change in the tiedor mirrored boards or dashboards of the same or other owners.

Boards and widgets may be part of a platform that may enable users tointeract with information in real time in collaborative work systemsinvolving electronic collaborative word processing documents. Electroniccollaborative word processing documents (and other variations of theterm) as used herein are not limited to only digital files for wordprocessing, but may include any other processing document such aspresentation slides, tables, databases, graphics, sound files, videofiles or any other digital document or file. Electronic collaborativeword processing documents may include any digital file that may providefor input, editing, formatting, display, and/or output of text,graphics, widgets, objects, tables, links, animations, dynamicallyupdated elements, or any other data object that may be used inconjunction with the digital file. Any information stored on ordisplayed from an electronic collaborative word processing document maybe organized into blocks. A block may include any organizational unit ofinformation in a digital file, such as a single text character, word,sentence, paragraph, page, graphic, or any combination thereof. Blocksmay include static or dynamic information, and may be linked to othersources of data for dynamic updates. Blocks may be automaticallyorganized by the system, or may be manually selected by a user accordingto preference. In one embodiment, a user may select a segment of anyinformation in an electronic word processing document and assign it as aparticular block for input, editing, formatting, or any other furtherconfiguration.

An electronic collaborative word processing document may be stored inone or more repositories connected to a network accessible by one ormore users through their computing devices. In one embodiment, one ormore users may simultaneously edit an electronic collaborative wordprocessing document. The one or more users may access the electroniccollaborative word processing document through one or more user devicesconnected to a network. User access to an electronic collaborative wordprocessing document may be managed through permission settings set by anauthor of the electronic collaborative word processing document. Anelectronic collaborative word processing document may include graphicaluser interface elements enabled to support the input, display, andmanagement of multiple edits made by multiple users operatingsimultaneously within the same document.

Various embodiments are described herein with reference to a system,method, device, or computer readable medium. It is intended that thedisclosure of one is a disclosure of all. For example, it is to beunderstood that disclosure of a computer readable medium describedherein also constitutes a disclosure of methods implemented by thecomputer readable medium, and systems and devices for implementing thosemethods, via for example, at least one processor. It is to be understoodthat this form of disclosure is for ease of discussion only, and one ormore aspects of one embodiment herein may be combined with one or moreaspects of other embodiments herein, within the intended scope of thisdisclosure.

Embodiments described herein may refer to a non-transitory computerreadable medium containing instructions that when executed by at leastone processor, cause the at least one processor to perform a method.Non-transitory computer readable mediums may be any medium capable ofstoring data in any memory in a way that may be read by any computingdevice with a processor to carry out methods or any other instructionsstored in the memory. The non-transitory computer readable medium may beimplemented as hardware, firmware, software, or any combination thereof.Moreover, the software may preferably be implemented as an applicationprogram tangibly embodied on a program storage unit or computer readablemedium consisting of parts, or of certain devices and/or a combinationof devices. The application program may be uploaded to, and executed by,a machine comprising any suitable architecture. Preferably, the machinemay be implemented on a computer platform having hardware such as one ormore central processing units (“CPUs”), a memory, and input/outputinterfaces. The computer platform may also include an operating systemand microinstruction code. The various processes and functions describedin this disclosure may be either part of the microinstruction code orpart of the application program, or any combination thereof, which maybe executed by a CPU, whether or not such a computer or processor isexplicitly shown. In addition, various other peripheral units may beconnected to the computer platform such as an additional data storageunit and a printing unit. Furthermore, a non-transitory computerreadable medium may be any computer readable medium except for atransitory propagating signal.

The memory may include a Random Access Memory (RAM), a Read-Only Memory(ROM), a hard disk, an optical disk, a magnetic medium, a flash memory,other permanent, fixed, volatile or non-volatile memory, or any othermechanism capable of storing instructions. The memory may include one ormore separate storage devices collocated or disbursed, capable ofstoring data structures, instructions, or any other data. The memory mayfurther include a memory portion containing instructions for theprocessor to execute. The memory may also be used as a working scratchpad for the processors or as a temporary storage.

Some embodiments may involve at least one processor. A processor may beany physical device or group of devices having electric circuitry thatperforms a logic operation on input or inputs. For example, the at leastone processor may include one or more integrated circuits (IC),including application-specific integrated circuit (ASIC), microchips,microcontrollers, microprocessors, all or part of a central processingunit (CPU), graphics processing unit (GPU), digital signal processor(DSP), field-programmable gate array (FPGA), server, virtual server, orother circuits suitable for executing instructions or performing logicoperations. The instructions executed by at least one processor may, forexample, be pre-loaded into a memory integrated with or embedded intothe controller or may be stored in a separate memory.

In some embodiments, the at least one processor may include more thanone processor. Each processor may have a similar construction, or theprocessors may be of differing constructions that are electricallyconnected or disconnected from each other. For example, the processorsmay be separate circuits or integrated in a single circuit. When morethan one processor is used, the processors may be configured to operateindependently or collaboratively. The processors may be coupledelectrically, magnetically, optically, acoustically, mechanically or byother means that permit them to interact.

Consistent with the present disclosure, disclosed embodiments mayinvolve a network. A network may constitute any type of physical orwireless computer networking arrangement used to exchange data. Forexample, a network may be the Internet, a private data network, avirtual private network using a public network, a Wi-Fi network, a LANor WAN network, and/or other suitable connections that may enableinformation exchange among various components of the system. In someembodiments, a network may include one or more physical links used toexchange data, such as Ethernet, coaxial cables, twisted pair cables,fiber optics, or any other suitable physical medium for exchanging data.A network may also include a public switched telephone network (“PSTN”)and/or a wireless cellular network. A network may be a secured networkor unsecured network. In other embodiments, one or more components ofthe system may communicate directly through a dedicated communicationnetwork. Direct communications may use any suitable technologies,including, for example, BLUETOOTH™, BLUETOOTH LE™ (BLE), Wi-Fi, nearfield communications (NFC), or other suitable communication methods thatprovide a medium for exchanging data and/or information between separateentities.

Certain embodiments disclosed herein may also include a computing devicefor generating features for work collaborative systems, the computingdevice may include processing circuitry communicatively connected to anetwork interface and to a memory, wherein the memory containsinstructions that, when executed by the processing circuitry, configurethe computing device to receive from a user device associated with auser account instruction to generate a new column of a single data typefor a first data structure, wherein the first data structure may be acolumn oriented data structure, and store, based on the instructions,the new column within the column-oriented data structure repository,wherein the column-oriented data structure repository may be accessibleand may be displayed as a display feature to the user and at least asecond user account. The computing devices may be devices such as mobiledevices, desktops, laptops, tablets, or any other devices capable ofprocessing data. Such computing devices may include a display such as anLED display, augmented reality (AR), virtual reality (VR) display.

Certain embodiments disclosed herein may include a processor configuredto perform methods that may include triggering an action in response toan input. The input may be from a user action or from a change ofinformation contained in a user's table, in another table, acrossmultiple tables, across multiple user devices, or from third-partyapplications. Triggering may be caused manually, such as through a useraction, or may be caused automatically, such as through a logical rule,logical combination rule, or logical templates associated with a board.For example, a trigger may include an input of a data item that isrecognized by at least one processor that brings about another action.

In some embodiments, the methods including triggering may cause analteration of data and may also cause an alteration of display of datacontained in a board or in memory. An alteration of data may include arecalculation of data, the addition of data, the subtraction of data, ora rearrangement of information. Further, triggering may also cause acommunication to be sent to a user, other individuals, or groups ofindividuals. The communication may be a notification within the systemor may be a notification outside of the system through a contact addresssuch as by email, phone call, text message, video conferencing, or anyother third-party communication application.

Some embodiments include one or more of automations, logical rules,logical sentence structures and logical (sentence structure) templates.While these terms are described herein in differing contexts, in abroadest sense, in each instance an automation may include a processthat responds to a trigger or condition to produce an outcome; a logicalrule may underly the automation in order to implement the automation viaa set of instructions; a logical sentence structure is one way for auser to define an automation; and a logical template/logical sentencestructure template may be a fill-in-the-blank tool used to construct alogical sentence structure. While all automations may have an underlyinglogical rule, all automations need not implement that rule through alogical sentence structure. Any other manner of defining a process thatrespond to a trigger or condition to produce an outcome may be used toconstruct an automation.

Other terms used throughout this disclosure in differing exemplarycontexts may generally share the following common definitions.

In some embodiments, machine learning algorithms (also referred to asmachine learning models or artificial intelligence in the presentdisclosure) may be trained using training examples, for example in thecases described below. Some non-limiting examples of such machinelearning algorithms may include classification algorithms, dataregressions algorithms, image segmentation algorithms, visual detectionalgorithms (such as object detectors, face detectors, person detectors,motion detectors, edge detectors, etc.), visual recognition algorithms(such as face recognition, person recognition, object recognition,etc.), speech recognition algorithms, mathematical embedding algorithms,natural language processing algorithms, support vector machines, randomforests, nearest neighbors algorithms, deep learning algorithms,artificial neural network algorithms, convolutional neural networkalgorithms, recursive neural network algorithms, linear machine learningmodels, non-linear machine learning models, ensemble algorithms, and soforth. For example, a trained machine learning algorithm may comprise aninference model, such as a predictive model, a classification model, aregression model, a clustering model, a segmentation model, anartificial neural network (such as a deep neural network, aconvolutional neural network, a recursive neural network, etc.), arandom forest, a support vector machine, and so forth. In some examples,the training examples may include example inputs together with thedesired outputs corresponding to the example inputs. Further, in someexamples, training machine learning algorithms using the trainingexamples may generate a trained machine learning algorithm, and thetrained machine learning algorithm may be used to estimate outputs forinputs not included in the training examples. In some examples,engineers, scientists, processes and machines that train machinelearning algorithms may further use validation examples and/or testexamples. For example, validation examples and/or test examples mayinclude example inputs together with the desired outputs correspondingto the example inputs, a trained machine learning algorithm and/or anintermediately trained machine learning algorithm may be used toestimate outputs for the example inputs of the validation examplesand/or test examples, the estimated outputs may be compared to thecorresponding desired outputs, and the trained machine learningalgorithm and/or the intermediately trained machine learning algorithmmay be evaluated based on a result of the comparison. In some examples,a machine learning algorithm may have parameters and hyper parameters,where the hyper parameters are set manually by a person or automaticallyby a process external to the machine learning algorithm (such as a hyperparameter search algorithm), and the parameters of the machine learningalgorithm are set by the machine learning algorithm according to thetraining examples. In some implementations, the hyper-parameters are setaccording to the training examples and the validation examples, and theparameters are set according to the training examples and the selectedhyper-parameters.

FIG. 1 is a block diagram of an exemplary computing device 100 forgenerating a column and/or row oriented data structure repository fordata consistent with some embodiments. The computing device 100 mayinclude processing circuitry 110, such as, for example, a centralprocessing unit (CPU). In some embodiments, the processing circuitry 110may include, or may be a component of, a larger processing unitimplemented with one or more processors. The one or more processors maybe implemented with any combination of general-purpose microprocessors,microcontrollers, digital signal processors (DSPs), field programmablegate array (FPGAs), programmable logic devices (PLDs), controllers,state machines, gated logic, discrete hardware components, dedicatedhardware finite state machines, or any other suitable entities that canperform calculations or other manipulations of information. Theprocessing circuitry such as processing circuitry 110 may be coupled viaa bus 105 to a memory 120.

The memory 120 may further include a memory portion 122 that may containinstructions that when executed by the processing circuitry 110, mayperform the method described in more detail herein. The memory 120 maybe further used as a working scratch pad for the processing circuitry110, a temporary storage, and others, as the case may be. The memory 120may be a volatile memory such as, but not limited to, random accessmemory (RAM), or non-volatile memory (NVM), such as, but not limited to,flash memory. The processing circuitry 110 may be further connected to anetwork device 140, such as a network interface card, for providingconnectivity between the computing device 100 and a network, such as anetwork 210, discussed in more detail with respect to FIG. 2 below. Theprocessing circuitry 110 may be further coupled with a storage device130. The storage device 130 may be used for the purpose of storingsingle data type column-oriented data structures, data elementsassociated with the data structures, or any other data structures. Whileillustrated in FIG. 1 as a single device, it is to be understood thatstorage device 130 may include multiple devices either collocated ordistributed.

The processing circuitry 110 and/or the memory 120 may also includemachine-readable media for storing software. “Software” as used hereinrefers broadly to any type of instructions, whether referred to assoftware, firmware, middleware, microcode, hardware descriptionlanguage, or otherwise. Instructions may include code (e.g., in sourcecode format, binary code format, executable code format, or any othersuitable format of code). The instructions, when executed by the one ormore processors, may cause the processing system to perform the variousfunctions described in further detail herein.

FIG. 2 is a block diagram of computing architecture 200 that may be usedin connection with various disclosed embodiments. The computing device100, as described in connection with FIG. 1, may be coupled to network210. The network 210 may enable communication between different elementsthat may be communicatively coupled with the computing device 100, asfurther described below. The network 210 may include the Internet, theworld-wide-web (WWW), a local area network (LAN), a wide area network(WAN), a metro area network (MAN), and other networks capable ofenabling communication between the elements of the computingarchitecture 200. In some disclosed embodiments, the computing device100 may be a server deployed in a cloud computing environment.

One or more user devices 220-1 through user device 220-m, where ‘m’ inan integer equal to or greater than 1, referred to individually as userdevice 220 and collectively as user devices 220, may be communicativelycoupled with the computing device 100 via the network 210. A user device220 may be for example, a smart phone, a mobile phone, a laptop, atablet computer, a wearable computing device, a personal computer (PC),a smart television and the like. A user device 220 may be configured tosend to and receive from the computing device 100 data and/or metadataassociated with a variety of elements associated with single data typecolumn-oriented data structures, such as columns, rows, cells, schemas,and the like.

One or more data repositories 230-1 through data repository 230-n, where‘n’ in an integer equal to or greater than 1, referred to individuallyas data repository 230 and collectively as data repository 230, may becommunicatively coupled with the computing device 100 via the network210, or embedded within the computing device 100, Each data repository230 may be communicatively connected to the network 210 through one ormore database management services (DBMS) 235-1 through DBMS 235-n. Thedata repository 230 may be for example, a storage device containing adatabase, a data warehouse, and the like, that may be used for storingdata structures, data items, metadata, or any information, as furtherdescribed below. In some embodiments, one or more of the repositoriesmay be distributed over several physical storage devices, e.g., in acloud-based computing environment. Any storage device may be a networkaccessible storage device, or a component of the computing device 100.

FIG. 3 is an exemplary embodiment of a presentation of an electroniccollaborative word processing document 301 via an editing interface oreditor 300. The editor 300 may include any user interface components 302through 312 to assist with input or modification of information in anelectronic collaborative word processing document 301, For example,editor 300 may include an indication of an entity 312, which may includeat least one individual or group of individuals associated with anaccount for accessing the electronic collaborative word processingdocument. User interface components may provide the ability to format atitle 302 of the electronic collaborative word processing document,select a view 304, perform a lookup for additional features 306, view anindication of other entities 308 accessing the electronic collaborativeword processing document at a certain time (e.g., at the same time or ata recorded previous time), and configure permission access 310 to theelectronic collaborative word processing document. The electroniccollaborative word processing document 301 may include information thatmay be organized into blocks as previously discussed. For example, ablock 320 may itself include one or more blocks of information. Eachblock may have similar or different configurations or formats accordingto a default or according to user preferences. For example, block 322may be a “Title Block” configured to include text identifying a title ofthe document, and may also contain, embed, or otherwise link to metadataassociated with the title. A block may be pre-configured to displayinformation in a particular format (e.g., in bold font). Other blocks inthe same electronic collaborative word processing document 301, such ascompound block 320 or input block 324 may be configured differently fromtitle block 322. As a user inputs information into a block, either viainput block 324 or a previously entered block, the platform may providean indication of the entity 318 responsible for inputting or alteringthe information. The entity responsible for inputting or altering theinformation in the electronic collaborative word processing document mayinclude any entity accessing the document, such as an author of thedocument or any other collaborator who has permission to access thedocument.

Various embodiments of this disclosure describe unconventional systems,methods, and computer-readable media for enabling simultaneous groupediting of electronically stored documents. While multiple users maysimultaneously edit electronically stored documents, it may be difficultto distinguish which group or groups the edits correspond to. It may bedifficult to define groups and limit which users are able to editanother user's previous edits, it may be beneficial to separate themultiple users into separate defined groups. Edits made by a first groupmay need to be identified and distinguished from edits made by a secondgroup. Further it may be beneficial to automatically identify new usersas belonging to the first group, second group, or a new third groupbased on characteristics of the new users. It may be beneficial torequire permission before members become part of a group and make editson behalf of the group. Furthermore, it may be beneficial to decide whenalterations made by one group may be viewed by the other group. Byenabling groups of editors collaborating on an electronic document, asystem may increase its processing efficiency by sorting users intodetermined, different groups so that users belonging to certain groupsmay be identified together and streamline the system's tracking processfor edits from numerous computing devices associated with different useraccounts.

Some disclosed embodiments may involve systems, methods, andcomputer-readable media for enabling simultaneous group editing ofelectronically stored documents. A group may refer to one or moremembers associated with an aggregate where each member may include anyentity such as a person, client, group, account, device, system,network, business, corporation, or any other user accessing acollaborative electronic document through an associated computing deviceor account. An electronically stored document, as used herein, mayinclude a file containing any information that is stored in electronicformat, such as text files, word processing documents, Portable DocumentFormat (pdf), spreadsheets, sound clips, audio files, movies, videofiles, tables, databases, or any other digital file. Editing may includeadding, deleting, rearranging, modifying, correcting, or otherwisechanging the data or information in an electronically stored document.Group editing may be simultaneous in that multiple users may edit anelectronically stored document in real time or near real time. Groupediting may also occur at different times. For example, a first group(e.g., company A) may have employees and a second group (e.g., companyB) may have their own employees, and both the first group and the secondgroup may have their respective employees accessing and editing anelectronic collaborative word processing document stored in acloud-based repository, discussed in further detail below.

Some disclosed embodiments may include accessing a collaborativeelectronic document. Accessing may refer to gaining authorization orentry to download, upload, copy, extract, update, edit, or otherwisereceive, retrieve, or manipulate data or information. For example, for aclient device (e.g. a computer, laptop, smartphone, tablet, VR headset,smart watch, or any other electronic display device capable of receivingand sending data) to access a collaborative electronic document, theclient device may send a request to retrieve information stored in arepository associated with a system, which may require authentication orcredential information, and the system processor may confirm or denyauthentication information supplied by the client device as needed.Accessing an electronic word processing document may include retrievingthe electronic word processing document from a storage medium, such as alocal storage medium or a remote storage medium. A local storage mediummay be maintained, for example, on a local computing device, on a localnetwork, or on a resource such as a server within or connected to alocal network. A remote storage medium may be maintained in the cloud,or at any other location other than a local network. In someembodiments, accessing the electronic word processing document mayinclude retrieving the electronic word processing document from a webbrowser cache. Additionally or alternatively, accessing the electronicword processing document may include accessing a live data stream of theelectronic word processing document from a remote source. In someembodiments, accessing the electronic word processing document mayinclude logging into an account having a permission to access thedocument. For example, accessing the electronic word processing documentmay be achieved by interacting with an indication associated with theelectronic word processing document, such as an icon or file name, whichmay cause the system to retrieve (e.g., from a storage medium) aparticular electronic word processing document associated with theindication. A collaborative electronic document may be any processingdocument, including word processing, presentation slides, tables,databases, graphics, sound files, video files or any other digitaldocument or file (e.g. a text, programming language, video,presentation, audio, image, design, document, spreadsheet, tabular,virtual machine, a link or shortcut, an image file, a video file, avideo game file, an audio file, a playlist file, an audio editing file,a drawing file, a graphic file, a presentation file, a spreadsheet file,a project management file, a pdf file, a page description file, acompressed file, a computer-aided design file, a database, a publishingfile, a font file, a financial file, a library, a web page, a personalinformation manager file, a scientific data file, a security file, asource code file, or any other type of file which may be stored in adatabase). Accessing a collaborative electronic document may involveretrieving data through any electrical medium such as one or moresignals, instructions, operations, functions, databases, memories, harddrives, private data networks, virtual private networks, Wi-Fi networks,LAN or WAN networks, Ethernet cables, coaxial cables, twisted paircables, fiber optics, public switched telephone networks, wirelesscellular networks, BLUETOOTH™, BLUETOOTH LE™ (BLE), Wi-Fi, near fieldcommunications (NFC), or any other suitable communication method thatprovide a medium for exchanging data.

For example, a collaborative electronic document may be stored inrepository 230-1 as shown in FIG. 2. Repository 230-1 may be configuredto stem software, files, or code, such as a collaborative electronicdocument developed using computing device 100 or user device 220-1.Repository 230-1 may further be accessed by computing device 100, userdevice 220-1, or other components of system 200 for downloading,receiving, processing, editing, or viewing, the collaborative electronicdocument. Repository 230-1 may be any suitable combination of datastorage devices, which may optionally include any type or combination ofslave databases, load balancers, dummy servers, firewalls, back-updatabases, and/or any other desired database components. In someembodiments, repository 230-1 may be employed as a cloud service, suchas a Software as a Service (SaaS) system, a Platform as a Service(PaaS), or Infrastructure as a Service (laaS) system. For example,repository 230-1 may be based on infrastructure of services of AmazonWeb Services™ (AWS), Microsoft Azure™, Google Cloud Platform™, CiscoMetapod™, Joyent™, vmWare™, or other cloud computing providers.Repository 230-1 may include other commercial file sharing services,such as Dropbox™, Google Docs™, or iCloud™. In some embodiments,repository 230-1 may be a remote storage location, such as a networkdrive or server in communication with network 210. In other embodimentsrepository 230-1 may also be a local storage device, such as localmemory of one or more computing devices (e.g., computing device 100) ina distributed computing environment.

Some disclosed embodiments may include linking a first entity and asecond entity to form a first collaborative group, and linking a thirdentity and a fourth entity to form a second collaborative group. Therelational terms herein such as “first” and “second” are used only todifferentiate an entity or operation from another entity or operation,and do not require or imply any actual relationship or sequence betweenthese entities or operations. An entity may include a person, client,group, account, device, system, network, business, corporation, or anyother user accessing a collaborative electronic document through anassociated computing device or account, Linking a first entity and asecond entity may include joining, connecting, associating, or otherwiseestablishing a relationship between the first and second entity. Acollaborative group may refer to any combination of entities linkedtogether to form an aggregate entity. The first entity and second entitymay be linked to form a first collaborative group. The first entity andsecond entity may be manually or automatically linked. For example, thefirst entity and second entity may be manually assigned to acollaborative group by an administrator, supervisor, or any other user.For example, the user may input instructions into a computing devicethat associates two entities together to form a group. Automatic linkingmay include automatically assigning the first and second entities to acollaborative group based on one or more settings, conditions,instructions, or other factors including but not limited to the companythey work for, a shared network drive, the domain associated with theiremail address, the team they are on, a predetermined or predefined list,randomly, or any other way of classifying entities. For example, thesystem may determine that the first user associated with a first emailaddress (e.g., employee1@company1.com) and the second user associatedwith a second email address (e.g., employee2@company1.com) belong to afirst collaborative group (e.g., Company1) because the email addressesinclude the same or similar email address domains. Once an entity isassigned to a collaborative group, the entity may also be unlinked fromthe collaborative group and may be further reassigned to anothercollaborative group.

Some disclosed embodiments may include linking a third entity and afourth entity to form a second collaborative group. The definitions ofaccessing a collaborative electronic document, collaborative group, andlinking, as described above in connection with the first collaborativegroup applies equally to the second collaborative group. However, thespecific functionality associated with each collaborative group mayvary. In one embodiment for example, the first collaborative group maybe linked automatically while the second collaborative group may belinked manually.

In some embodiments a first collaborative group may include a pluralityof first additional entities linked to first and second entities, and asecond collaborative group may include a plurality of second additionalentities linked to third and fourth entities. An additional entity maybe any added, extra, or supplemental entity to the first and secondentities as discussed previously above. For example, a first additionalentity may be linked to the first collaborative group (e.g., alreadyincluding the first and second entities) so there are three entities inthe first collaborative group: the first entity, the second entity, andthe first additional entity. One or more first additional entities maybe linked to the first collaborative group. Similarly, for example, asecond additional entity may be linked to the second collaborative groupso there are three entities in the second collaborative group: the thirdentity, the fourth entity, and the second additional entities. One ormore second additional entities may be linked to the secondcollaborative group. Additional entities may be included at theformation of the collaborative group or after the collaborative groupwas formed. As a non-limiting example, the first additional entity maybe linked to the first and second entities at or near the same time asthe formation of the first collaborative group. Alternatively, forexample, the first additional entity may be linked to the first entityand second entity at a time after the formation of the firstcollaborative group. The plurality of first and second additionalentities may be linked to the first and second collaborative groupsconsistent with linking steps previously discussed. Similarly, the firstand second additional entities may be unlinked from the collaborativegroups and reassigned to other collaborative groups as needed by manualor automatic steps. For example, if a first additional entity (e.g.,employee3@company1.com) was linked to a first collaborative group, butthen leaves the company, the system may detect that the email address nolonger exists and remove the first additional entity from the firstcollaborative group. Additionally or alternatively, if the firstadditional entity (e.g., employee3@company1.com) was linked to a firstcollaborative group (e.g., Company1), but then changes companies toCompany2, the system may detect the updated email address domain for thefirst additional entity and in response, link the first additionalentity with the second collaborative group (e.g., Company2).

Some disclosed embodiments may include receiving a first alteration by afirst entity to a collaborative electronic document, tagging the firstalteration by the first entity with a first collaborative groupindicator, receiving a second alteration to the collaborative electronicdocument by a second entity, and tagging the second alteration by thesecond entity with the first collaborative group indicator. Analteration may include any edit, addition, deletion, comment, change,subtraction, rearrangement, correction, or any other modification of theinformation in a collaborative electronic document. Receiving thealteration may include receiving an input from any computing deviceassociated with an entity that provides instructions to at least oneprocessor to manipulate data or other information contained in thecollaborative electronic document. For example, receiving an alterationmay include a computing device associated with a user manually inputtinginformation or instructions, sending a signal associated with a changeof information (e.g. a status change), or any other information that maybe input, detected, or transmitted. Tagging the alteration may includeidentifying, marking, labeling, associating, classifying, or otherwiseindicating the source of the first alteration through an identifier suchas metadata that may be stored in a repository. For example, the systemmay receive an input from a computing device that adds metadata to anassociated alteration to link and store the metadata with the alterationin a repository so that any collaborating entity may access the taggedinformation. A first collaborative group indicator may include anyidentification for the collaborative group, such as one or more colors,names, shapes, symbols, graphical indicators, images, pictures,alphanumeric characters, avatars, videos, VR or AR object, metadata, orany combination thereof. For example, the system may receive an edit tothe collaborative electronic document made by a first employee ofCompany1, that results in a rendering of a collaborative groupindicator, such as a logo of Company1, in the collaborative electronicdocument so any entity accessing the document can see the logo ofCompany1 associated with the edit. The system may receive a second editto the collaborative electronic document by a different, second employeeof Company1. The second edit may result in the rendering of acollaborative group indicator, such as the logo of Company1, that alsoappears in the collaborative electronic document so any entity accessingthe document can see the logo of Company1 associated with the secondedit. Further, the system may tag the alteration by the second entitywith the first collaborative group indicator because the system mayrecognize that the second entity belongs to the first collaborativegroup, as discussed previously above. For example, the first and secondemployees at Company1 may make edits, and the system may determine theybelong to the same first collaborative group (e.g., Company1). As aresult, the system may display an indicator associated with edits madeby both with the same color associated with Company1.

Some disclosed embodiments may include receiving a third alteration to acollaborative electronic document by a third entity, tagging the thirdalteration by the third entity with a second collaborative groupindicator, receiving a fourth alteration from the fourth entity to thecollaborative electronic document, and tagging the fourth alteration bythe fourth entity with the second collaborative group indicator. Asstated above, the relational terms herein such as “first,” “second,”“third,” and so on are used only to differentiate an entity or operationfrom another entity or operation, and do not require or imply any actualrelationship or sequence between these entities or operations. Thedefinitions of an alteration, tagging, and a collaborative groupindicator, as described above in connection with the first collaborativegroup indicator applies equally to the second collaborative groupindicator. However, the specific functionality associated with eachcollaborative group may vary. The second collaborative group indicatormay be different from the first collaborative group indicator. Thesecond collaborative group indicator may distinguish the third andfourth alterations from the first and second alterations. For example,the second collaborative group indicator may be the color red, while thefirst collaborative group indicator may be the color blue. Additionally,or alternatively, the second collaborative group indicator may be thename of a company, while the first collaborative group indicator may bethe name of a different company. This may reduce the processing time andstorage requirements associated with a collaborative electronicdocument, since the system may only need to track and store informationby collaborative groups after the system determines the collaborativegroup associations, rather than track and store information according toindividual users.

For example, as shown in FIG. 3, the collaborative electronic documentmay be an electronic collaborative word processing document 301 via anediting interface or editor 300. In FIG. 4, may illustrate anotherembodiment of a collaborative electronic document 400. A first entity402 (identified by a thumbnail) and a second entity 404 (identified by athumbnail) may be represented by a thumbnail or any other graphical oralphanumeric indicator in the collaborative electronic document. A thirdentity 412 (identified by an alphanumeric indicator) and a fourth entity414 (identified by an alphanumeric indicator) may be represented bytheir name. The first entity 402 and the second entity 404 may be linkedto form the first collaborative group, manually or automatically by thesystem as discussed above. The first collaborative group may beindicated by the first collaborative group indicator 410, the name“Company 1.” The third entity 412 and the fourth entity 414 may belinked to form the second collaborative group, which may be indicated bythe second collaborative group indicator 420, “Company 2 logo.” Thefirst entity 402 may make a comment, “Great title” on part of thecollaborative electronic document, which may be the first alteration406. The second entity 404 may make a deletion which may be the secondalteration 408. Both the first alteration 406 and the second alteration408 may be tagged by the system with the first collaborative groupindicator 410 as a result of recognizing that the first alteration 406and the second alteration 408 were made by entities belonging to thefirst collaborative group. The third entity 412 may add text, “themiddle of the text” to part of the document, which may be the thirdalteration 416. The fourth entity 414 may add a “NEW IMAGE” to thedocument, which may be the fourth alteration 418. The third alteration416 and the fourth alteration 418 may be tagged with the secondcollaborative group indicator 420 as a result of recognizing that thethird alteration 416 and the fourth alteration 420 were made by entitiesbelonging to the second collaborative group.

Aspects of this disclosure may prevent a second collaborative group frommaking edits to a first alteration and a second alteration. Preventingmay refer to inhibiting, not allowing, disabling, blocking, or otherwiselimiting any action. Making edits may refer to removing, deleting,cutting, adding to, correcting, rewriting, modifying, or making anyother alteration. Preventing entities from the second collaborativegroup from making edits to alterations made by the first collaborativegroup, for example, may lock the display of information altered by thefirst collaborative group so that entities from the second collaborativegroup may only view the altered information. For example, if the firstalteration made by the first entity of the first collaborative groupadds an image to the collaborative electronic document, the third entityand fourth entity of the second collaborative group may not be allowedto change, delete, or interact with the image. In some embodiments, thesystem may also provide a notification to the entities of the secondcollaborative group that they may be restricted from making alterations.In other embodiments, the system may render the information altered bythe first collaborative group in a different format or any otherindication (e.g., text that is in gray font) to indicate to the secondcollaborative group that the system is preventing it from making editsto the altered information.

For example, in FIG. 4, the first entity 402 and the second entity 404may not be able to delete the third alteration 416 (“the middle of thetext”) that was added by the third entity 412 (identified by thealphanumeric characters “Sarah”). Similarly, the first entity 402 andthe second entity 404 may not be able to delete the fourth alteration418 “NEW IMAGE.”

Some disclosed embodiments may include a processor configured to receivean attempt by a fifth entity to change a first alteration, accesspermissions settings, determine whether the fifth entity possess apermission enabling change of the first alteration, and upondetermination of a change-enabling permission, apply the change to thefirst alteration. Receiving an attempt by a fifth entity to change thefirst alteration may include the system receiving a signal from acomputing device associated with the fifth entity that containsinstructions for making an edit to the first alteration. A change mayinclude any instructions to edit, remove, delete, add, correct, rewrite,rearrange, or otherwise modify information in the collaborativeelectronic document. Permission settings may include any configurationsthat can grant, allow, restrict, limit, check, verify or otherwisedetermine user access associated with a collaborative electronicdocument. Permission settings may be any permissions associated with acollaborative electronic document that may be defined by a user orpredefined by the system. As discussed above, user access to anelectronic collaborative word processing document may be managed throughpermission settings set by an author of the electronic collaborativeword processing document. Accessing permission settings may includeperforming a lookup in a storage or repository containing permissionconfigurations for authorized accounts that access a collaborativeelectronic document. A permission enabling change may include anyapproval, consent, agreement, assent, permit, or other authorization ofan entity to make an alteration. Determining whether the fifth entitypossess a permission may refer to verifying, regulating, or otherwisedetermining if the fifth entity has a change-enabling permission. Thismay involve performing a lookup in a repository of authorized entitiesto verify whether the accessing entity is listed in a list ofpre-authorized entities for accessing information. Applying the changeto the first alteration may include adopting the instructions to makethe change and manipulation the information contained in the firstalteration, as discussed above, and carrying out the instructions andstoring the change in the repository. After carrying out theseinstructions, the system may be configured to then determine whether thefifth entity belongs to a previously recorded collaborative group orbelongs to a new collaborative group, discussed in further detail below.

For example, a permission may be based on a pre-determined condition orother requirement stored in a repository that may be determined based ona processor performing a lookup in the repository and determining thatan entity accessing the collaborative electronic document meets athreshold and is authorized to access the information or functionalityin the collaborative electronic document. Alternatively, permission maybe determined, assigned, or otherwise designated by a user or any otherentity associated with the collaborative electronic document. Forexample, permission or authorization to change may only be allowed bycertain entities such as an administrator, manager, group, team, orother authorized individuals or entities. For example, the system maydetermine that the fifth entity does not possess change-enablingpermission after the system performs a lookup of authorized entities inthe stored permission settings. Alternatively, for example, it may bedetermined that the fifth entity does possess change-enablingpermission. Some disclosed embodiments may require permission orapproval from the first entity, the second entity, or both the first andthe second entity in order for the fifth entity to possesschange-enabling permission. This may ensure that all entities associatedwith the first collaborative group authorize each other's alterationsbefore releasing the alterations to the other collaborative groups onthe collaborative electronic document. Additionally or alternatively, itmay be required that a different entity (i.e. administrator, manager, orother user) determine whether the fifth entity possess change-enablingpermission. In some disclosed embodiments, for example, each attempt bya fifth entity to make a change to an alteration may require determiningwhether the fifth entity possess change-enabling permission.Alternatively, for example, whether the fifth entity possesschange-enabling permission may only need to be determined once, whichmay then be recorded in the repository as a permission setting regardingthe fifth entity for accessing the collaborative electronic document.

For example, in FIG. 2, a fifth entity may access a collaborativeelectronic document from user device 220-2 via Network 210 and stored inrepository 230-1. After accessing the collaborative electronic document,the fifth entity may see alterations made on user device 220-1 by afirst entity of a first collaborative group. The fifth entity mayattempt to change the alterations made by the first entity. Thecomputing device 100 may then determine, by looking up instructionsstored in its memory whether the fifth entity (user device 220-2) haspermission to change the first alteration. It may be determined that thefifth entity has permission to change, and the changes may then bestored in repository 230-1. The next entity that accesses thecollaborative electronic document on user device 220-m, via Network 210,may see the changes made by the fifth entity to the collaborativeelectronic document.

In some aspects of the disclosure, it may be determined that a fifthentity possesses the permission, based on a determination that the fifthentity is associated with the first collaborative group. Determinationthat the fifth entity is associated with the first collaborative groupmay include analyzing characteristics of the fifth entity, comparingthem to the characteristics of the first collaborative group, andidentifying a similar or matching characteristic such that the fifthentity is related to the first collaborative group, consistent with thediscussion above. For example, it may be required that the fifth entitybe a part of the first collaborative group (i.e., linked to the firstentity and the second entity) to possess a change-enabling permission.Alternatively, for example, it may be determined that the fifth entitymay possess a change-enabling permission and may not be a part of thefirst collaborative group. Alternatively, some embodiments may includeat least one processor further configured to recognize a fifth entity asa member of a third collaborative group with permission to changealterations of a first collaborative group, to permit the change to afirst alteration, and to tag the change with a third collaborative groupindicator. Recognizing the fifth entity as a member of a thirdcollaborative group may include determining that the fifth entity may belinked to an additional collaborative group (e.g., the thirdcollaborative group) or that it may not belong to either the firstcollaborative group or the second collaborative group. For example, thesystem may analyze characteristics of the fifth entity and recognizethat it is associated with Company3, different from Company1 that isassociated with a first collaborative group, and different from Company2that is associated with a second collaborative group. The system maydetermine that the fifth entity is associated with a third collaborativegroup and that the third collaborative group has permission to changealterations made by the first collaborative group (Company1). Thechanges may be tagged or otherwise associated with a third collaborativegroup indicator (e.g. the logo of Company3). Recognizing that the thirdcollaborative group with permission to change alterations of the firstcollaborative group may include determining that the third collaborativegroup is authorized to change the first alteration based on default orconfigured permission settings, consistent with the disclosure discussedpreviously above. For example, the third collaborative group may bepermitted to change alterations of the first collaborative group but maynot be permitted to change alterations of the second collaborativegroup. Alternatively, the third collaborative group may be permitted tochange alterations of the first and second collaborative group.Consistent with the discussion above, permitting the change to the firstalteration may refer to allowing or authorizing an entity to edit, add,delete, comment on, change, subtract, rearrange, correct or any othergranting of authority to modify the first alteration. Tagging the changewith a third collaborative group indicator may include identifying,marking, labeling, associating, classifying, or otherwise indicating thesource of the change through an identifier (e.g., the thirdcollaborative group indicator). For example, tagging a change mayinclude associating metadata with the change that may be stored in arepository and not necessarily displayed. In other examples, tagging thechange may include associating an indicator (e.g., graphical,alphanumeric, or a combination thereof) that may be presented in amanner to indicate additional information relating to or otherwiseidentifying the collaborative group.

For example, FIG. 5A, illustrates a display of a collaborativeelectronic document 400. A fifth entity 502A, represented by a thumbnailimage, may be recognized as a member of a third collaborative group withpermission to change alterations of the first collaborative group. Fifthentity 502A may reply to the comment “Great title” (the first alteration406) with their own comment “I think it could be shorter” which may bethe fifth alteration 504A. The third collaborative group indicator 506Amay indicate that the fifth alteration 504A came from the thirdcollaborative group. Additionally or alternatively, the fifth entity502A may decide to also edit (not shown) the second alteration 408. Forexample, the fifth entity 502A may add text to the second alteration 408and the added text (not shown), which may also be indicated by the thirdcollaborative group indicator 506A.

Further, some embodiments of this disclosure may include receiving anattempt by a sixth entity to change the first alteration, accesspermissions settings, determine whether that the sixth entity lackspermission enabling change of the first alteration, and generates aduplicate version of the collaborative electronic document in which thesixth entity is permitted to change the first alteration. Generating aduplicate version of the collaborative electronic document may includecopying and reproducing the information contained in a collaborativeelectronic document in a new electronic document. Determining that anentity lacks permission enabling change of the first alteration mayinclude performing a lookup of authorized entities, through permissionsettings as discussed above, that an entity may not be authorized tochange the first alteration and restricting the entity from making thechange. By way of example, it may be determined that the sixth entitydoes not have permission to change the first alteration in thecollaborative electronic document. In response to this determination,the system may generate a duplicate of the collaborative electronicdocument for the sixth entity to make alterations without affecting theoriginal collaborative electronic document. For example, the firstentity may be a manager with change-enabling permission while the sixthentity may be a subordinate without change-enabling permission. Thesixth entity may attempt to change the first alteration, the system,through a lookup in a repository of authorized entities, may determinethat the sixth entity does not have permission to make changes to thefirst alteration, which results in the system generating a duplicateversion of the collaborative electronic document for the sixth entity tomake edits such that the sixth entity may work on an independent versionof the collaborative electronic document without affecting the originaldocument.

By way of example in FIG. 6, a sixth entity 602 (identified by athumbnail) may attempt to change the first alteration 406 in thecollaborative electronic document 400 (as shown in FIG. 4). It may bedetermined that the sixth entity 602 does not have permission to changethe first alteration, so the sixth alteration may not appear in thecollaborative electronic document 400, However, a new duplicatecollaborative electronic document 600 may be generated for the sixthentity that allows the sixth entity to change the first alterationwithout affecting the original collaborative electronic document 400.This may enable the sixth entity to edit the collaborative electronicdocument 400 in a duplicate copy without being delayed by the lack ofpermission to edit the original collaborative electronic document 400.

Some disclosed embodiments may involve rendering a display of acollaborative electronic document, wherein the rendered display includespresenting a first collaborative group indicator in association with afirst alteration and a second alteration, and wherein the rendereddisplay includes a second collaborative group indicator displayed inassociation with a third alteration and a fourth alteration. Rendering adisplay of the collaborative electronic documents may include causing apresentation of information contained in an electronic document on adevice, as described previously above, such that a user associated witha computing device may view and interact with the information in thecollaborative electronic document. Rendering the display may includeproviding the collaborative electronic document to an entity byoutputting one or more signals configured to result in the presentationof the collaborative electronic document on a screen, or other surface,through a projection, or in a virtual space with the entity. This mayoccur, for example, on one or more of a touchscreen, a monitor, AR or VRdisplay, or any other means previously discussed and discussed furtherbelow. The electronic word processing document may be presented, forexample, via a display screen associated with the entity's computingdevice, such as a PC, laptop, tablet, projector, cell phone, or personalwearable device. The electronic word processing document may also bepresented virtually through AR or VR glasses, or through a holographicdisplay. Other mechanisms of presenting may also be used to enable theentity to visually comprehend the presented information. Presenting thefirst collaborative group indicator in association with the firstalteration and the second alteration may include displaying or renderingthe first collaborative group indicator corresponding to the first andsecond alterations in a manner that is next to, below, above, togetherwith, in conjunction with, related to, embedded in, or otherwiseconnected to the first alteration and the second alteration, By way ofexample, both the first alteration and the second alteration may beidentified as originating from the first collaborative group by theirassociation with the first collaborative group indicator. The firstcollaborative group indicator may be identical for the first alterationand the second alteration. For example, the first collaborative groupindicator may be a graphical rendering of a logo of a company.Additionally or alternatively, the first collaborative group indicatormay be different for the first alteration and the second alteration. Forexample, the first collaborative group indicator in association with thefirst alteration may include a display of the logo of a company and athumbnail indicating the identity of the first entity, while the firstcollaborative group indicator in association with the second alterationmay be the display of the logo of a company and a thumbnail indicatingthe identity of the second entity.

As stated above, the relational terms herein such as “first,” “second,”“third,” and so on are used only to differentiate an entity or operationfrom another entity or operation, and do not require or imply any actualrelationship or sequence between these entities or operations. Thedefinitions of rendering a display and presenting or displaying thecollaborative group indicator in association with the alteration appliesequally to the second collaborative group. However, the specificfunctionality associated with each collaborative group may vary. Forexample, the second collaborative group indicator may be below the thirdand fourth alterations, while the first collaborative group indicatormay be next to the first and second alterations.

For example, FIG. 5A and FIG. 5B may show a display of the samecollaborative electronic document 400 at two different points in time,FIG. 5A may be at a point in time that is before FIG. 5B. FIG. 5Aillustrates an example situation when a display of the renderedcollaborative electronic document 400 does not show the third alterationor the fourth alteration. The third alteration 416 and the fourthalteration 418 may require approval from the third entity 414 (e.g.“John”) before being displayed. FIG. 5B, a later point in time, may showa disclosed embodiment of the collaborative electronic document 400after the third entity 414 (John) approves the alteration through aninteraction with the document (e.g. clicking an approval button or anyother gesture or command instructing the same) and allows the display ofthe third alteration 416 and the fourth alteration 418. That is, forexample, the first collaborative group 410 may not be able to see thethird alteration 416 and the fourth alteration 418 (e.g. FIG. 5A) untilthe third entity 414 approves the third alteration 416 and the fourthalteration 418, at which point the first collaborative group 410 mayview the third alteration 416 and the fourth alteration 418 (e.g. FIG.5B).

Aspects of this disclosure may include at least one processor configuredto display a first collaborative group indicator in association with afirst alteration and a second alteration, including a first instance ofthe first collaborative group indicator displayed in association withthe first alteration and a second instance of the first collaborativegroup indicator displayed in association with the second alteration.Further, a third alteration and a fourth alteration may include a firstinstance of a second collaborative group indicator displayed inassociation with the third alteration and a second instance of thesecond collaborative group indicator displayed in association with thefourth alteration. An instance of the first collaborative groupindicator may refer to an occasion, occurrence, display or anypresentation of the collaborative group indicator. For example, multipleinstances of the first collaborative group indicator may be rendered inconjunction with edits from the first and second entity alterations suchthat each of the alterations from the first collaborative group may beidentified with a common indicator.

For example, presenting the first collaborative group indicator inassociation with the first alteration and the second alteration may besimultaneous, or near simultaneous as the first alteration and secondalteration are made in the collaborative electronic document.Alternatively, for example, presenting the first collaborative groupindicator in association with the first alteration and the secondalteration may be completed after, at a time other than when thealterations are made. Some disclosed embodiments may additionallyrequire approval before presenting the first alteration, the secondalteration, or both. For example, the first alteration made by the firstentity may require approval from the second entity before the firstinstance of the first collaborative group indicator may be displayed inassociation with the first alteration. This may ensure that all entitiesassociated with the first collaborative group authorize each other'salterations before releasing the alterations to the other collaborativegroups on the collaborative electronic document. Additionally, oralternatively, the first alteration my require the approval by anotherentity (i.e. an administrator, manager, or other user) before the firstinstance of the first collaborative group indicator may be displayed inassociation with the first alteration. Similarly, it may be required forthe first entity to select an interactive element (e.g. any element in auser interface which may be interacted with through a mouse cursor, atouchable area (as on a touchscreen our touchpad), eye movement (such aswith eye trackers), a gesture (such as may be detected by a camera), anapplication program interface (API) that receives a keyboard input, orany hardware or software component that may receive user inputs) orother means of activation before the first alteration may be displayedin association with the first collaborative group indicator. By anon-limiting example, the system may require the first entity to press abutton indicating approval of the first alteration before the firstalteration is displayed. Alternatively, the system may require a secondentity to press a button indicating approval of the first alteration.Additionally or alternatively, the system may require both the first andthe second entity to press a button indicating approval of the firstalteration.

FIG. 7 illustrates a block diagram of an example process 700 forenabling simultaneous group editing of electronically stored documents.While the block diagram may be described below in connection withcertain implementation embodiments presented in other figures, thoseimplementations are provided for illustrative purposes only, and are notintended to serve as a limitation on the block diagram. In someembodiments, the process 700 may be performed by at least one processor(e.g., the processing circuitry 110 in FIG. 1) of a computing device(e.g., the computing device 100 in FIGS. 1 and 2) to perform operationsor functions described herein and may be described hereinafter withreference to FIGS. 4 to 6 by way of example. In some embodiments, someaspects of the process 700 may be implemented as software (e.g., programcodes or instructions) that are stored in a memory (e.g., the memoryportion 122 in FIG. 1) or a non-transitory computer-readable medium. Insome embodiments, some aspects of the process 700 may be implemented ashardware (e.g., a specific-purpose circuit). In some embodiments, theprocess 700 may be implemented as a combination of software andhardware. FIG. 7 may include process blocks 702 to 724:

At block 702, the processing means may be configured to access acollaborative electronic document, consistent with the earlierdisclosure.

At block 704, the processing means may involve linking a first entityand a second entity to form a first collaborative group, as discussedpreviously in the disclosure above.

At block 706, the processing means may be configured to link a thirdentity and a fourth entity to form a second collaborative group, asdiscussed previously in the disclosure above.

At block 708, the processing means may be configured to receive a firstalteration by the first entity to the collaborative electronic document,as discussed previously in the disclosure above.

At block 710, the processing means may be configured to tag the firstalteration by the first entity with a first collaborative groupindicator, as discussed previously in the disclosure above.

At block 712, the processing means may involve receiving a secondalteration to the collaborative electronic document by the secondentity, as discussed previously in the disclosure above.

At block 714, the processing means may involve tagging the secondalteration by the second entity with the first collaborative groupindicator, as discussed previously in the disclosure above.

At block 716 the processing means may further be configured to receive athird alteration to the collaborative electronic document by the thirdentity, consistent with the earlier disclosure.

At block 718, the processing means may be further configured to tag thethird alteration by the third entity with a second collaborative groupindicator, as discussed previously in the disclosure above.

At block 720, the processing means may involve receiving a fourthalteration from the fourth entity to the collaborative electronicdocument, as discussed previously in the disclosure above.

At block 722, the processing means may involve tagging the fourthalteration by the fourth entity with the second collaborative groupindicator, as discussed previously in the disclosure above.

At block 722, the processing means may be further configured to render adisplay of the collaborative electronic document, as discussedpreviously in the disclosure above.

Various embodiments of this disclosure describe unconventional systems,methods, and computer-readable media for enabling granular rollback ofhistorical edits in an electronic document. While users may undo editsmade to an electronic documents, it may be difficult to distinguish theentire document from a specific portion of a document where a user maywant to undo. It may be difficult to only undo edits made to a specificportion of a document without also undoing edits made to other portionsof a document. Further, it may be difficult to view a history of editsmade to a specific portion of a document. It may be beneficial to enableviewing of historical edits made to a specific portion of the document.It may be beneficial to enable choosing which, if any, previous editshould be restored. It may be beneficial to allow changing only aspecific portion of a document to a previous edit. By enabling granularrollback of historical edits in an electronic document, it may increasethe efficiency of editing electronic documents by reducing the number offiles that need to be stored in memory for version control, whichthereby also increases the overall system's processing speed ofprocessing historical edits for just a single electronic file.

Some disclosed embodiments may involve systems, methods, andcomputer-readable media for enabling granular rollback of historicaledits in an electronic document. Edits may include any addition,deletion, rearrangement, modification, correction, or other change madeto the data or information in an electronic document. Historical editsmay be any edit made previously, in the past, prior to, or otherwisemade at a time before the present time. An electronic document, as usedherein, may be any file containing any information that is stored inelectronic format, such as text files, word processing documents,Portable Document Format (pdf), spreadsheets, sound clips, audio files,movies, video files, tables, databases, or any other digital file.Granular rollback of historical edits in an electronic document mayrefer to any review, analysis, or assessment of past edits made to asubset, detailed display, or other specific portion of an electronicdocument. Additionally, enabling granular rollback may refer toallowing, permitting, or otherwise authorizing rollback of historicaledits on any selected portion of information an electronic document. Forexample, a user may be working in an electronic document and review theprevious edits made to a specific paragraph of the document, or anyother organization of information in the electronic document (e.g., acharacter, a word, a sentence, a paragraph, a page, or any combinationthereof). Granular rollback of historical edits may be stored,retrieved, and/or transmitted by a user within an electronic document.For example, the system may be configured to automatically enable thegranular rollback of historical edits. Alternatively, the system may beconfigured to only enable granular rollback of historical edits whenprompted by a user (e.g., by a toggle on and off feature).

Some disclosed embodiments may include accessing an electronic document,having an original form, Accessing may refer to gaining authorization orentry to download, upload, copy, extract, update, edit, or otherwisereceive, retrieve, or manipulate data or information through anelectrical medium. For example, for a client device (e.g., a computer,laptop, smartphone, tablet, VR headset, smart watch, or any otherelectronic display device capable of receiving and sending data) toaccess an electronic document, it may require authentication orcredential information, and the processor may confirm or denyauthentication information supplied by the client device as needed.Accessing an electronic document may include retrieving the electronicdocument from a storage medium, such as a local storage medium or aremote storage medium. A local storage medium may be maintained, forexample, on a local computing device, on a local network, or on aresource such as a server within or connected to a local network. Aremote storage medium may be maintained in the cloud, or at any otherlocation other than a local network. In some embodiments, accessing theelectronic document may include retrieving the electronic document froma web browser cache. Additionally or alternatively, accessing theelectronic document may include accessing a live data stream of theelectronic document from a remote source. In some embodiments, accessingthe electronic document may include logging into an account having apermission to access the document. For example, accessing the electronicdocument may be achieved by interacting with an indication associatedwith the electronic document, such as an icon or file name, which maycause the system to retrieve (e.g., from a storage medium) a particularelectronic document associated with the indication. Having an originalform may include any new, initial, prior, previous, first or otheredition, display, instance, or other version of an electronic document.The original form may be a new, unedited electronic document (e.g., thegeneration of a new document such that it is a blank document withoutany populated data or information). Alternatively, the original form maybe an already edited or existing version of an electronic document. Forexample, a user may generate a new, blank document that is an originalform of the document. Alternatively or additionally, a user may save analready edited document to a location on a network and that may be anoriginal form of an electronic document. For example, a user maydetermine the original form of an electronic document, such as, by aninput (e.g., the selection of a button) that stores information orinstructions in a repository or other storage medium that, when executedby at least one processor, may identify the selected version as theoriginal form. For example, a user input may add metadata to a version(e.g., the original form of an electronic document) to link and storethe metadata with that version of the electronic document in arepository. Alternatively or additionally, the system may automaticallydetermine the original form of an electronic document. By way of anon-limiting example, the system may be configured to automaticallystore, in a repository or other storage medium, the data and informationassociated with an electronic document as the original form after thefirst time the electronic document is saved. Similarly, for example, thesystem may be configured to automatically store, in a repository orother storage medium, the data and information associated with anelectronic document as the original form when the electronic document isfirst created.

FIG. 8, for example, may be the original form 802 of electronic document800. For example, in FIG. 2, a user may save, via network 210, theoriginal form of an electronic document (e.g., 802 of FIG. 8) inrepository 230-1. Repository 230-1 may be configured to store software,files, or code, such as the original form of an electronic documentdeveloped using computing device 100 or user device 220-1. A computingdevice 100, user device 220-1, or a different user device 220-2 mayaccess, as discussed above, the electronic document in its original formfrom repository 230-1. Repository 230-1 may further be accessed bycomputing device 100, user device 220-1, or other components of system200 for downloading, receiving, processing, editing, or viewing, theelectronic document. Repository 230-1 may be any suitable combination ofdata storage devices, which may optionally include any type orcombination of slave databases, load balancers, dummy servers,firewalls, back-up databases, and/or any other desired databasecomponents. In some embodiments, repository 230-1 may be employed as acloud service, such as a Software as a Service (SaaS) system, a Platformas a Service (PaaS), or Infrastructure as a Service (laaS) system. Forexample, repository 230-1 may be based on infrastructure of services ofAmazon Web Services™ (AWS), Microsoft Azure™, Google Cloud Platform™,Cisco Metapod™, Joyen™, vmWare™, or other cloud computing providers.Repository 230-1 may include other commercial file sharing services,such as Dropbox™, Google Docs™ or iCloud™. In some embodiments,repository 230-1 may be a remote storage location, such as a networkdrive or server in communication with network 210. In other embodimentsrepository 230-1 may also be a local storage device, such as localmemory of one or more computing devices (e.g., computing device 100) ina distributed computing environment.

Some disclosed embodiments may include recording at a first time, firstedits to a specific portion of an electronic document, recording at asecond time, second edits to the specific portion of the electronicdocument, and recording at a third time, third edits to the specificportion of the electronic document. The relational terms herein such as“first,” “second,” and “third” are used only to differentiate an edit oroperation from another edit or operation, and do not require or implyany actual relationship or sequence between these edits or operations.Recording edits may refer to storing, saving, keeping, maintaining, orpreserving alterations made to an electronic document in memory orrepository (e.g., a data structure). Recording may be done automaticallyor manually. For example, as discussed in more detail below, the editsmay be recorded at a default or predetermined time intervals (e.g., byseconds, minutes, hours, days, or any other time increment).Additionally or alternatively, edits may be recorded when prompted byuser action. For example, edits may be recorded when a user saves theelectronic document. Similarly, for example, edits may be recorded whena user closes the electronic document. Further, for example, edits maybe recorded by the selection of an interactive element (e.g., pressing abutton). The edits may be stored in any non-transitory computer-readablemedium. At least one processor may then perform a lookup of permissionsettings to confirm whether the computing device has authorization tomake the edit. In a situation where authorization is confirmed, thesystem may then implement and store the edit with the electronicdocument such that any other computing devices accessing the documentmay retrieve the recorded edit. In another situation where authorizationis not confirmed for the editing entity, the system may lock theinformation in the electronic document such that the information in theelectronic document is unable to be altered by the editing entity.

Edits, as referenced above, may refer to any addition, deletion,rearrangement, modification, correction, or other change made to thedata or information in an electronic document. For example, edits to anelectronic document may be made by one entity, by a group, or by theprocessor (e.g., via a logical rule for carrying out the task of makingan alteration). Alternatively, edits to an electronic document may bemade my more than one entity. Recording edits at a time may include anystoring an instance of the completed edits at a distinct point in time(e.g., in response to an input from a user indicating an instruction torecord), instance, occurrence, interval, or other measure of time thatmay be determined according to preference or according to a default. Forexample, a first time may be any point in time occurring before a secondtime. Alternatively or additionally, a first time may be any interval oftime occurring before any second time. A specific portion of theelectronic document may be any subset, piece, segment, page, section, orother part of the electronic document. For example, the electronicdocument may be a word processing document, and the specific portion ofthe electronic document may be a letter, word, sentence, part of asentence, paragraph, page, or any other portion of the electronic wordprocessing document. For example, recording at a first time, first editsto a specific portion of the electronic document may include associatingmetadata with the edits that may be stored in a repository so at leastone processor may identify the instance of those edits. Recording at afirst time, first edits to a specific portion of the electronic documentmay involve, for example, storing the addition of a new sentence to thespecific portion of the electronic document in a repository.

By way of example, in FIG. 1 and FIG. 2, at least one processor mayimplement recording a first edit made to a specific portion of anelectronic document by storing the edit in storage 130 in FIG. 1, or ina repository 230-1 in FIG. 2. Similarly, the at least on processor mayimplement recording a second edit made to the specific portion of anelectronic document by storing it in storage 130 in FIG. 1, or in arepository 230-1 in FIG. 2. A computing device 100 or a user device 220may access, as discussed above, the stored edits and may display (e.g.,on a screen, other surface, through a projection, or in a virtual space)data and information from the first edit, the second edit, or both thefirst edit and the second edit, as discussed in more detail below.

Some disclosed embodiments may include receiving at a fourth time, aselection of a specific portion. Receiving a selection may include thesystem accepting a user input from a computing device associated with auser that indicates instructions to make a selection. The user input maybe transmitted over a network to a repository where the electronicdocument is stored. A selection may be any action taken to elect, pick,designate, or otherwise choose a portion of the electronic document. Forexample, a selection may be a mouse click, a user input, a mouseover, ahighlight, a hover, a touch on a touch sensitive surface, a keystroke, amovement in a virtual interface, or any other action indicating a choiceof a specific portion of the electronic document. For example, aselection may be using a mouse to click and highlight (e.g., by mouseclick and drag) of a specific portion of an electronic document.Additionally or alternatively, a selection may require an additionalclick of an activatable element, such as a button.

In FIG. 9, for example, the selection may be made by highlighting thespecific portion of text 902 (e.g., “This is our new time slider and weare so excited to share it with our users, this is really amazingfeature”) and then clicking an icon button 910, For example, selecting aspecific portion may include any signal or indication that meets athreshold for carrying out instructions for rendering a historicalinterface (see below for more detail).

In response to a selection, some disclosed embodiments may include,rendering a historical interface enabling viewing of an original form ofthe selection, first edits, second edits, and third edits. Rendering thehistorical interface may include causing a display of data orinformation in the historical interface via a display device. Forexample, previous versions (e.g., the original form of the selection,the first edits, the second edits, or the third edits) may be displayed,which may require the at least one processor to perform a lookup of theprevious version in storage or a repository, and then the system mayimplement and display the previous version in the historical interface.Each previous version (e.g., the original form of the selection, thefirst edits, the second edits, or the third edits) may, for example,include metadata associated with the version allowing the at least oneprocessor to identify the version and distinguish it from the otherversions. A historical interface may refer to one or a combination of agraphical user interface (GUI), software interface, a web page, anapplication interface, or any other interface that enables interactionbetween a human and a machine. The historical interface may include, insome embodiments, an interface with activatable elements that displaysprevious, prior, past, and/or current versions of the electronicdocument or portions of the electronic document. As discussed above, theprevious versions (e.g., the original form of the selection, the firstedits, the second edits, or the third edits) may be stored in arepository or other storage medium. The interactive elements included inthe historical interface may include, for example, a mouse cursor, atouchable area (as on a touchscreen), keyboard input, or any hardware orsoftware component that can receive user inputs. The historicalinterface may include a pop-up window, a webpage, a drop-down menu orany graphical user interface element.

For example, in response to the selection, a rendering of the historicalinterface may appear inside of, on top of, above, below, next to, orotherwise associated with a rendering of an electronic document. Forexample, the historical interface may appear in the same window as theelectronic document. Alternatively, the historical interface may appearin a new window. The historical interface may include one or moreinteractable visual elements, such as buttons, sliders, dials, or othervisual interactable graphics. Enabling viewing of an original form of aselection and edits may refer to any process or procedure that causes adisplay (e.g., on a screen, other surface, through a projection, or in avirtual space) of the original form of the selection, the first edits,the second edits, and the third edits. For example, as discussed above,the original form and edits made to the selection may be stored in arepository and include metadata so the at least one processor mayidentify the original form or edit. For example, all or some of theoriginal form of the selection, the first edits, the second edits, andthe third edits, or any combination thereof may be displayed in thehistorical interface at the same time. Alternatively, one of theoriginal form of the selection, the first edits, the second edits, andthe third edits may be displayed in the historical interface at a time.For example, user interaction may enable changing the display from oneedit to another with a historical interface that may include a sliderthat enables a user to change between different displays or forms of thespecific portion of the electronic document, such as, a display of theoriginal form of the selected portion, a display of the selected portionafter first edits were made to the electronic document, a display of theselected portion after second edits were made to the electronicdocument, and a display of the selected portion after the third editswere made to the electronic document. In response to the userinteracting with the historical interface, such as moving the slider toa marker, discussed in more detail below, associated with an edit, theprocessor may look up additional data or information stored andassociated with the edit, for example, the day and time the edits weremade.

For example, FIG. 10A to FIG. 10C may include exemplary renderings of ahistorical interface 1000A. For example, in FIG. 10A to FIG. 10C, aftera selection of a specific portion of a document 902 is made, asdiscussed above, (e.g., “This is our new time slider and we are soexcited to share it with our users, this is really amazing feature”), ahistorical interface 1000A may be rendered on a display of an associatedcomputing device. The historical interface 1000A may enable viewing ofthe original form of the selection (not shown) by presenting theoriginal form or presenting a link or any other activatable element toaccess the original form. As shown in FIG. 10A, the historical interface1000A may enable viewing of the selected portion 902 after first edits904 (“and we are so excited”) were made at a first time 1002A. As shownin FIG. 108, the historical interface 1000A may enable viewing of thesecond edits 906 (e.g., “to share it with our users.”) made at a secondtime 1002B. And as shown in FIG. 10C, the historical interface 1000A mayenable viewing of the third edits 908 (e.g., “this is really amazingfeature”) made at a third time 1002C.

In some disclosed embodiments, a historical interface may include aninteractive timeline enabling rollback of edits to markers on thetimeline denotating the original form of the selection, the first edits,the second edits, and the third edits. An interactive timeline may referto any rendered interface (e.g., a graphical user interface) that mayinclude any number of activatable visual elements that may be activatedvia any interaction (e.g., a cursor hover, mouse click, gesture,keyboard input) that send instructions to the processor, such as forretrieving historical edits from memory and for presenting those editson a display. For example, as discussed above, an interactive timelinemay allow a user to change between different displays, versions, orforms of the specific portion of the electronic document selected. Forexample, each marker on the interactive timeline may be associated witha different version of the electronic document and, as discussed above,each version (e.g., the original form and each edit) may be stored in arepository and include metadata so the at least one processor mayidentify the and display the version associated with each marker.

Markers on the timeline may include any visual rendering such as a sign,dash, symbol, icon, pointer, or other indicator that denotes,distinguishes, or represents a time in which edits were made in anelectronic document. For example, one or any combination of the originalform of the selection, the first edits, the second edits, and the thirdedits may be denoted by markers on the timeline and may be rendered atspecific locations in the timeline to suggest a relative time an editwas made in comparison to other edits or the original form. Markers on atimeline may represent different edits made to the electronic document.For example, a first marker on the timeline may indicate first editsmade at a first time. Similarly, a second marker on the timeline mayindicate second edits made at a second time. Each marker may representdifferent edits made to the specific portion of the electronic document.For example, as discussed above, the system may perform a lookup anddisplay the historical edits associated with the marker selected by auser. Alternatively, two or more markers may render the same display,for example, if no edits were made to the specific portion of theelectronic document between two or more time intervals represented bymarkers. Enabling rollback of edits to 4 t) markers on the timeline mayrefer to authorizing a user to interact with the timeline to activatethe interactable elements (e.g., the markers) that may cause theprocessor to retrieve historical edits associated with each of themarkers available on the timeline. Rollback may include causing are-rendering of a display to present historical edits at a particulartime. Selecting a marker (e.g., by a mouse click, gesture, cursormovement, or any other action that results in the selection of a marker)on the timeline may display edits associated with that marker. Forexample, if the first marker on the timeline represents the first editsmade at a first time, selecting the first marker may render a display ofthe first edits. Similarly, if the second marker on the timelinerepresents the second edits made at a second time, a selection of thesecond marker may render a display of the second edits, A marker on thetimeline may represent the original form of an electronic document.Further, a marker on the timeline may represent the most recent, orcurrent form of the document.

For example, in FIG. 2, a historical interface with markers may bedisplayed on user device 220-1, and a user may select, via anactivatable element on user device 220-1, one of the markers. Inresponse to the selection, the system, via network 210, may look up inrepository 230-1 the historical edit associated with the selectedmarker. For example, in FIG. 10A, a selection of a marker associatedwith edits may be made by moving a rocket slider 1006A to a markerlocation. For example, selecting a marker associated with the firstedits 1004A may enable a rollback of the selected portion to the firstedits 904 (“and we are so excited”), made at a first time represented bya time indicator 1002A. Similarly, as shown in FIG. 10B, selecting amarker associated with the second edits 1004B may enable a rollback ofthe selected portion to the second edits 906 (“to share it with ourusers.”), made at a second time represented by a time indicator 1002B.Further, in FIG. 10C, selecting a marker associated with the third edits1004C may enable a rollback of the selected portion to the third edits908 (“this is really amazing feature”), made at a third time representedby a time indicator 1002C. The marker associated with the third edits1004C may be the most recent edits made to the specific portion of theelectronic document 902.

In some disclosed embodiments, the first edits may be made by a firstentity, the second edits may be made by a second entity and the thirdedits may be made by a third entity, and the markers may enableidentification of a particular entity associated with a particular edit.In further disclosed embodiments the markers may indicate an identity ofan associated entity responsible for an associated edit. An entity mayinclude a person, client, group, account, device, system, network,business, corporation, or any other user accessing an electronicdocument through an associated computing device or account. Markersenabling identification of a particular entity associated with aparticular edit may include visual indicators linking, detecting,recognizing, classifying, associating, or otherwise determining arelationship or connection between edits made to an electronic documentwith an entity. A particular edit may be any alteration made to anelectronic document, such as any of the first, second, and third edits.Markets identifying an entity responsible for an associated edit mayrefer to any visual indicator that presents information associated for aresponsible entity or account that made a correlating alteration to anelectronic document. For example, a computing device may associatemetadata with any edit made to an electronic document with data orinformation associated with an entity that makes each edit, and thesystem may be configured to store the metadata with the edit in arepository. For example, based on one or more settings, conditions,instructions, or other factors, a system may be configured to identifythe entity responsible for an associates edit. Identifying informationmay include the IP address, MAC address, the user ID associated with auser device (such as user device 220 of FIG. 2), or any other comparableinformation that can be used to identify a particular user account, auser device, information of a user (e.g., name, image, email address),or other means of identifying a specific entity. In some embodiments,edits made by a specific user device may be associated with an entity,information regarding the specific user device may be stored as metadatawith the edit such that the processor may retrieve the metadata andpresent an indicator identifying the specific user or associatedcomputing device that is responsible for the edit. The first edits maybe made by a first entity, and the processor may record, as discussedabove, the identity of the first entity with the first edits in arepository. As a result, when receiving a selection of a portion of thedocument including the first edits, the rendered historical interfacemay present a marker representing when the first edits were made, andthe marker may include any visual indicator representing and/oridentifying the first entity, such as an avatar, a thumbnail image,alphanumeric text, or a combination thereof. Additionally, the secondedits may be made by a second entity, and a second marker representingwhen the second edits may include any identifying visual indicatorassociated with the second entity, similar to the markers of the firstentity. When markers are rendered on a historical interface, each markermay be rendered in similar or different manners. For example, a firstmarker associated with when a first edit was made may include agraphical indicator of a depiction of a llama to represent a firstentity responsible for making the first edit. In the same historicalinterface, a second marker associated with when a second edit was mademay include a visual indicator including textual information such asinitials or a name that identifies a second entity responsible formaking the second edits.

In FIG. 10A, an exemplary historical interface 1000A may include markerspresented as thumbnail images identifying the particular entityassociated with a particular edit. One marker 1004A may include athumbnail identifying the particular entity (e.g. “Sagie”) associatedwith the particular edit 904.

In some disclosed embodiments the first edits, the second and the thirdedits may be each associated with a common entity. Being associated witha common entity may refer to each of the first, the second, and thethird edits being made by or attributed to the same, similar,equivalent, or other associated entity or entities. For example, acommon entity may be a person, client, group, account, device, system,network, business, corporation, or any other user or users accessing anelectronic document through an associated computing device or account. Acommon entity on an associated computing device may make multiple editsto an electronic document, such as the first edits, the second edits,and the third edits as discussed previously above. Additionally oralternatively, the first edits, the second edits, and the third editsmay be made on different user devices associated with a common entity(e.g., each of the edits are made by different employees at the samecompany). The first edit, second edit, and third edit may be representedby different markers, or may be represented by a common marker.

For example, in FIGS. 10A to 10C, each marker associated with edits, maybe associated with different entities. For example, the markerassociated with the first edits 1004A in FIG. 10A may be associated witha user device (“Sagie's device”). The marker associated with the thirdedits 1004C may be associated with a different user device (“Guy'sdevice”). In alternative embodiments not shown, the markers in thehistorical interface may be associated with a common entity, such as thesame user device, the same user account, or member of the same company.

Some disclosed embodiments may include applying a time interval todocument edits wherein selection of a particular marker may cause apresentation of changes that occurred during the time interval. Infurther disclosed embodiments, the time interval may be user-definable.A time interval may be any period, duration, length, or other amount oftime that may be defined with a beginning and end time. The timeinterval may be defined by the system. For example, the time intervalmay be a default time interval, instructing the system to record editsin a repository at each default time interval. Additionally andalternatively, the time interval may be manually or automaticallydefined. For example, the system may require a user to input a timeinterval to record edits in a repository at each input time interval.Applying a time interval to document edits may include assigning,allocating, or otherwise choosing a time interval during which edits aremade and recorded in a repository, as discussed above, as occurringduring that time interval. For example, as discussed above, edits may beevery change or any change made over a time interval. Applying the timeinterval may include sending instructions to the at least one processorto record in a repository the edits made during the time interval. Theedits made during the time interval may, for example, store metadatawith the edits in a repository so that the at least one processor mayperform a lookup in a repository for edits that have a timestamp withinthe time interval. A presentation of changes that occurred during thetime interval may include causing a display of the data and informationstored in a repository associated with the edits made during a timeinterval via a display device. The selection of a particular markercausing presentation of changes that occurred during the time intervalmay include, for example, displaying the data and information associatedwith the changes that occurred during a time interval on a user device.A time interval may be considered to be user-definable when the timeinterval is determined, defined, assigned, or otherwise designated by auser or any other entity on an associated computing device of theelectronic document. For example, the time interval may be defined by anadministrator, manager, group, team, or other authorized individuals orentities. For another example, there may be no edits made to a specificportion of the electronic document during a time interval (e.g., noalterations have been made). Alternatively, there may be edits to thespecific portion of the electronic document during a time interval.

For example, an authorized user on a user device 220-1 or a computingdevice 100 of FIGS. 1 and 2 may assign a time interval of one hour to anelectronic document. The system may carry out instructions to recordedits to the electronic document every hour and store the edits in arepository 230-1. The user may select, via an activatable element on ahistorical interface, a particular marker, which may represent aspecific hour. As discussed above, in response to the user's selectionof the specific hour, the at least one processor may perform a lookup ina repository for the edits made during that hour interval and maydisplay the edits made during the particular hour on a user device.Similarly, and as discussed above, if the user selects a differentmarker, representing a different hour, the at least one processor mayperform a lookup in a repository for the edits made during thatdifferent hour interval and may display the edits made during thedifferent hour interval on a user device.

In some disclosed embodiments the historical interface may be configuredto simultaneously display the first edit, the second edit, and the thirdedit. Simultaneously display may mean presenting any combination of orall of the first edit, the second edit, and the third edit at the sametime or near the same time. Display, as used herein, may include anyvisualization of data associated with the first edit, the second edit,and the third edit. For example, a historical interface may display thefirst edit above the second edit and the second edit above the thirdedit. This may allow a user to compare the edits at or near the sametime. For example, the at least one processor may retrieve from therepository data and information associated with each edit (e.g., anoriginal form, a first edit, a second edit, and/or a third edit) and mayrender a historical interface enabling viewing of the edits at the sametime. In other examples, the historical interface may render a displayof just the markers associated with each of the first, second, and thirdedits at the same time.

Some disclosed embodiments may include co-displaying a timeline in avicinity of a specific portion of an electronic document. Co-displayinga timeline in a vicinity of a specific portion of an electronic documentmay include enabling the visualization of a historical interface and aspecific portion of the electronic document at the same time, or nearthe same time in a common presentation on a display. For example, thehistorical interface may be shown above, below, next to, together with,side by side with, or otherwise near the specific portion of theelectronic document. This may enable a user to compare the specificportion of the electronic document selected with one or more of theedits made to the electronic document.

For example, in FIG. 10A, the historical interface 1000A may appear as apop-up window below the specific portion of the electronic document 902,and as a window above the rest of the information displayed in theelectronic document.

Some disclosed embodiments may include receiving an election of one ofthe original form of the electronic document, the first edits, thesecond edits, and the third edits, and upon receipt of the election,presenting a rolled-back display reflecting edits made to the specificportion of the electronic document, the rolled-back displaycorresponding to a past time associated with the election. Receiving anelection of one of the original form of the electronic document, thefirst edits, the second edits, or the third edits may include receivingan input from an associated computing device of a user or account thatindicates an intent for choosing, picking, deciding, appointing, orotherwise selecting (e.g., by a mouse click, gesture, cursor movement,or any other action by a user) the original form of the electronicdocument, the first edits, the second edits, or the third edits.Receiving an election may be a data input from a computer device. Forexample, receiving an election may include any signal or indication thatmeets a threshold for carrying out instructions for presenting arolled-back display, such as performing a lookup of data or informationstored in a repository associated with the election, A rolled-backdisplay reflecting edits made to the specific portion of the electronicdocument may include the presentation of any recorded version of thespecific portion of the electronic document as discussed previouslyabove. Presenting a rolled-back display reflecting edits made to thespecific portion of the electronic document upon receipt of the electionmay include outputting one or more signals configured to result in therendering of the alterations to the information in the specific portionof the electronic document associated with the previously receivedelection on any display methods, as described herein. The rolled-backdisplay corresponding to a past time associated with the election mayinclude the presentation of the selected version. For example, a usermay select the first edits, and in response, the system may perform alookup of the data and information stored in a repository associatedwith the first edits and present the first edits on a display device, asdiscussed previously above.

For example, after receiving an election of the original form (e.g., byselecting a graphical indicator associated with the original form on thehistorical interface), the rolled-back display may show the specificportion of the electronic document in an original form (e.g., before thefirst edits, the second edits, or the third edits were made).Alternatively, after receiving an election of the first edits in thehistorical interface, the rolled-back display may show the informationin the specific portion of the electronic document as it existed afterthe first edits were made to the specific portion. The rolled-backdisplay reflecting edits made to a specific version of the electronicdocument may present only the rolled-back display for the specificportion of the electronic document selected. For example, receiving anelection of the original form may present a rolled-back display of theoriginal form of the specific portion of the electronic document, whilethe rest of the electronic document (i.e. the portion of the electronicdocument that was not selected) may remain unchanged. An election mayinclude recording the selection of a new edit to the electronicdocument. For example, an election may be recorded and another selectionof the specific portion of the electronic document may render ahistorical interface that includes the election as an edit to a specificportion of the electronic document.

For example, FIG. 11 may represent a presentation of a rolled-backdisplay 1100 reflecting edits made to a specific portion of theelectronic document. For example, as discussed above, FIG. 10B may showa historical interface 1000A enabling viewing of the second edits 906(e.g., “to share it with our users.”) made at a second time 1002B to aspecific portion of the electronic document 902 (e.g., “This is our newtime slider and we are so excited to share it with our users, this isreally amazing feature”). An election may be received by clicking the“Restore” button 1006B. After the election is made, for example, FIG. 11may show a rolled-back display 1100.

FIG. 12 illustrates a block diagram of an example process 1200 forenabling granular rollback of historical edits in an electronicdocument. While the block diagram may be described below in connectionwith certain implementation embodiments presented in other figures,those implementations are provided for illustrative purposes only, andare not intended to serve as a limitation on the block diagram. In someembodiments, the process 1200 may be performed by at least one processor(e.g., the processing circuitry 110 in FIG. 1) of a computing device(e.g., the computing device 100 in FIGS. 1 and 2) to perform operationsor functions described herein and may be described hereinafter withreference to FIGS. 8 to 11 by way of example. In some embodiments, someaspects of the process 1200 may be implemented as software (e.g.,program codes or instructions) that are stored in a memory (e.g., thememory portion 122 in FIG. 1) or a non-transitory computer-readablemedium. In some embodiments, some aspects of the process 1200 may beimplemented as hardware (e.g., a specific-purpose circuit). In someembodiments, the process 1200 may be implemented as a combination ofsoftware and hardware.

FIG. 12 may include process blocks 1202 to 1218;

At block 1202, the processing means may be configured to access anelectronic document, having an original form, consistent with theearlier disclosure.

At block 1204, the processing means may be configured to record at afirst time, first edits to a specific portion of the electronicdocument, as discussed previously in the disclosure above.

At block 1206, the processing means may involve recording at a secondtime, second edits to the specific portion of the electronic document,as discussed previously in the disclosure above.

At block 1208, the processing means may involve recording at a thirdtime, third edits to the specific portion of the electronic document, asdiscussed previously in the disclosure above.

At block 1210, the processing means may be configured to receive at afourth time, a selection of the specific portion, as discussedpreviously in the disclosure above.

At block 1212, the processing means may be configured to render ahistorical interface enabling viewing of an original form of theselection, the first edits, the second edits, and the third edits, asdiscussed previously in the disclosure above.

At block 1214, the processing means may be configured to receive anelection of one of the original form of the electronic document, thefirst edits, the second edits, and the third edits, as discussedpreviously in the disclosure above.

At block 1216 the processing means may be further configured to presenta rolled-back display reflecting edits made to the specific portion ofthe electronic document, consistent with the earlier disclosure.

Various embodiments of this disclosure describe unconventional systems,methods, and computer-readable media for tracking on a slide-by-slidebasis, edits to presentation slides. In a stored deck of presentationslides, it may be difficult to only undo changes made to a particularslide without also undoing changes made to an entire deck of slides.Further, it may include difficult to view a history of changes made to aparticular slide. It may be beneficial to allow viewing of historicalchanges made to a particular slide. It may be beneficial to enablechoosing which, if any, previous changes should be reincorporated. Itmay be beneficial to enable editing of only particular slide of a deck.By tracking on a slide-by-slide basis, edits to presentation slides, itmay increase the efficiency of users editing stored decks ofpresentation slides by reducing the number of files that need to bestored in memory for version control, which thereby also increases theoverall system's processing speed of processing historical edits for astored slide deck.

Some disclosed embodiments may involve systems, methods, andcomputer-readable media for tracking on a slide-by-slide basis, edits topresentation slides. Tracking may include following, recording,maintaining, saving, or otherwise storing data and information. Forexample, data and information associated with an electronic file may betracked by storing associated data in memory or a repository.Presentation slides may include any program, digital document, or otherelectronic document used to store and display data or information.Presentation slides may include any presentable data and information asa single page of an electronic document, or multiple pages associatedwith each other in a deck. For example, a presentation slide may includeone or more of text, programming language, video, audio, image, design,document, spreadsheet, tabular, virtual machine, a link or shortcut. Thepresentation slide may be stored in any manner such as in an image file,a video file, a video game file, an audio file, a playlist file, anaudio editing file, a drawing file, a graphic file, a presentation file,a spreadsheet file, a project management file, a pdf file, a pagedescription file, a compressed file, a computer-aided design file, adatabase, a publishing file, a font file, a financial file, a library, aweb page, a personal information manager file, a scientific data file, asecurity file, a source code file, any other type of file, or otherpresentable data and information which may be stored in memory or arepository. A slide, as used herein and as discussed above, may includeany software, program, or electronic document used to present data orinformation that may be visually displayed in a single page. A slide mayinclude any subset, portion, page, document, sheet, or specific displayof a stored deck of presentation slides. Edits may include any addition,deletion, rearrangement, modification, correction, or other change madeto the data or information of a slide. Tracking on a slide-by-slidebasis, edits made to presentation slides may include storing orrecording alterations made to slides of a stored deck of presentationslides such that alterations made to the slides may be stored in andretrieved from memory or repository individually for each slide. Forexample, edits made to slides may include metadata that associates theedits with a specific slide and allows a processor to identify the editsas associated with the slide. In a deck of multiple slides, therepository may store alterations to each of the slides individually indifferent locations in the repository such that when the processorretrieves the data associated with a particular slide, the processoronly needs to access the repository once to retrieve all of the dataassociated with a particular slide. Tracking on a slide-by-slide basis,edits made to presentation slides may involve, for example, storing theaddition of a new sentence to the slide in a repository.

Some disclosed embodiments may include presenting a first windowdefining a slide pane for displaying a slide subject to editing. Therelational terms herein such as “first,” “second,” and “third” are usedonly to differentiate a window or operation from another window oroperation, and do not require or imply any actual relationship orsequence between these windows or operations. Presenting a window mayinclude causing a display of the data or information contained in adedicated portion of a display in a rendered visualization via a displaydevice, discussed in further detail below. For example, presenting awindow may include outputting one or more signals configured to resultin the display of a window on a screen, or other surface, throughprojection, or in virtual space. For example, presenting a window mayinclude visually representing or rendering, on a user device, the dataand information associated with a slide in a window. This may occur, forexample, on one or more of a touchscreen, a monitor, AR or VR display,or any other means previously discussed and discussed further below. Thewindow may be presented, for example, via a display screen associatedwith the entity's computing device, such as a PC, laptop, tablet,projector, cell phone, or personal wearable device. The window may alsobe presented virtually through AR or VR glasses, or through aholographic display. Other mechanisms of displaying may also be used toenable an entity to visually comprehend the presented information.

A window may include any defined area of a rendered display ofinformation dedicated to present information or data. For example, awindow may be associated with a width, height, aspect ratio, positionindicator, and/or any other information delineating the window's size orposition within an electronic file (e.g., represented in metadataassociated with the window). In some embodiments, a window may bepositioned and/or sized according to one or more inputs initiated by auser (e.g., dragging an outline of the window using a mouse). A slidepane may include any separate, defined, distinct, individual, or otherarea of a rendered display used for displaying, viewing, modifying,editing, or otherwise receiving input or interaction with one or moreslides. A slide pane may refer to a window as described above. A slidesubject to editing may be any slide that is actively presented foralteration that allows a user (e.g., by user inputs) to add, delete,rearrange, modify, correct, or otherwise change the data and informationin a particular slide. For example, a user may change the text of aslide in a slide subject to editing and may indicate to a processor aparticular slide for editing by selecting the particular slide to appearin a slide pane. A first window defining a slide pane for displaying aslide subject to editing may refer to a window rendering informationassociated with a slide, where the window may be an active editingdisplay that enables editing of that particular slide.

For example, a first window may display a slide on a computing device,such as computing device 100 (of FIG. 1) and may provide a user theability to make edits to the slide in the presented first window. Thefirst window may display a primary editing window for presentationslides. For example, in FIG. 13A, the first window 1302A may define aslide pane for displaying a slide subject to editing. In this example,the first window 1302A may allow a user to edit “Slide 1” since itappears in the first window 1302A acting as a window pane for activelyaltering a particular slide appearing in the first window 1302A.

Some disclosed embodiments may include presenting in a second window acurrent graphical slide sequence pane, for graphically displaying acurrent sequence of slides in the deck. A current graphical slide mayinclude any visual representation of an existing, recent, or presentversion of a slide. A current graphical slide sequence pane may refer toa window presenting, via a display device, one or more visualrepresentations of information that may be presented in a succession,series, chain, progression, arrangement, or other order according to adeck of slides that may be selected for presentation. Graphicallydisplaying may include rendering any visual representation, aid,demonstration, showing, or other presentation of data or information ina visual manner. Graphically displaying a current sequence of slides ina deck may include presenting the most recent, existing, latest, orpresent order of slides in a deck. For example, slides in a deck may benumbered one to four (e.g., it is the intent of a user for the slides topresent one after another in order) and may be presented with a previewof this sequence in a dedicated window of a screen. A deck may includeany series, set, or group of one or more slides of a presentation or anyother electronic document. Presenting in a second window a currentgraphical slide sequence pane may include displaying a particular deckof slides opened for presentation in the latest order of slidesdetermined by the deck on a display device. The second window maygraphically display the current sequence of slides in the deck in anyarrangement or order. For example, a slide deck may contain three slidesnumbered one, two, and three, and the second window may arrange anddisplay the first slide to the left of the second slide which itself mayappear to the left of the third slide. Alternatively, in the secondwindow, the first slide may be above the second slide, and the secondslide may be above the third slide.

For example, in FIG. 13A, a second window 1304A may render avisualization of a current graphical slide sequence pane for presentinga visual representation of the current order of the slides in a deck(e.g., Title, Slide 1, Slide 2, Slide 3, Slide 4, Slide 5).

Some disclosed embodiments may include presenting in a third window ahistorical graphical slide sequence pane for graphically presenting aformer sequence of slides in the deck. A historical graphical slide mayinclude any of a previous, past, or prior edition, rendering, display,or version of a slide that was previously stored in memory, A historicalgraphical slide sequence pane may include a window displaying, via adisplay device, data or information associated with retrievedhistorically stored versions of a particular slide according to aparticular order. For example, former versions of a slide may bedisplayed, which may require a processor to perform a lookup of theformer versions of a slide in storage or a repository, and then thesystem may implement and display the former version in a historicalgraphical slide sequence pane (i.e., the third window). Each previousversion of a slide may, for example, include metadata associated withthe version allowing the at least one processor to identify the versionand distinguish it from other previous versions and the current versionof the slide. Historical versions of a particular slide may be savedand/or stored manually or automatically in a repository or other storagemedium. For example, a historical version of a slide may be saved in arepository in response to a user input (e.g., the selection of a button)that stores information or instructions in a repository or other storagemedium that, when executed by at least one processor, may identify thehistorical version as associated with the particular slide. Additionallyor alternatively, for example, the system may be configured toautomatically store, in a repository or other storage medium, the dataand information associated with the historical version after a certainamount of time. Graphically presenting may include any visual rendering,representation, aid, demonstration, showing, or other display of data orinformation. A former sequence may include any order and arrangement ofthe previous versions of a slide. For example, the slides may bepresented in an order based on the time edits were made to the slide.For example, the earliest version of a slide, with edits made at anearliest time, may appear on top of each subsequent previous version ofthe slide. Alternatively, the most recent historical graphical slide mayappear on top and the earliest historical graphical slide may be on thebottom. Graphically presenting a former sequence of slides in the deckmay include displaying previous, past, historical, or prior editions,displays, instances, or other versions of a particular slide or formultiple slides. For example, presenting in a third window a historicalgraphical slide sequence pane for graphically presenting a formersequence of slides in the deck may include displaying historicalversions of a slide in the chronological order in which edits were madeto the slide. For example, the third window may display three priorversions of a slide, each version visually representing the slide atdifferent previous times. The processor may be configured to storedifferent versions of the slides in a repository or other storage mediumand may include metadata so a processor may identify each version of aslide and display each previous version in an any order. For example,graphically presenting a former sequence of slides in the deck mayinclude associating each slide with a different timestamp, and theprocessor may, in one lookup, retrieve all the data associated with aparticular slide (each historical graphical slide) from a repository anddisplay the historical graphical slides in chronological order, based onthe timestamp.

For example, in FIG. 13A, a third window 1306A may include a renderingof a historical graphical slide sequence pane and may present previousversions of a particular slide (e.g., Slide 1). As shown, the previousversions of the slide (e.g., Slide 1) may be ordered to representdifferent versions of the slide. For example, slide 1310A may representa first version of a particular slide, and 1314A may represent a laterversion of the particular slide (e.g., edits made after the edits madeto the first version) in a chronological manner.

Some disclosed embodiments may include accessing a stored deck ofpresentation slides. Accessing may include gaining authorization orentry to download, upload, copy, extract, update, edit, or otherwisereceive, retrieve, or manipulate data or information through anelectrical medium. For example, for a client device (e.g., a computer,laptop, smartphone, tablet. VR headset, smart watch, or any otherelectronic display device capable of receiving and sending data) toaccess a stored deck, it may require authentication or credentialinformation, and the processor may confirm or deny authenticationinformation supplied by the client device as needed. Accessing a storeddeck may include retrieving data through any electrical medium such asone or more signals, instructions, operations, functions, databases,memories, hard drives, private data networks, virtual private networks,Wi-Fi networks, LAN or WAN networks, Ethernet cables, coaxial cables,twisted pair cables, fiber optics, public switched telephone networks,wireless cellular networks, BLUETOOTH™, BLUETOOTH LE™ (BLE), Wi-Fi, nearfield communications (NFC), or any other suitable communication methodthat provide a medium for exchanging data, from a storage medium, suchas a local storage medium or a remote storage medium. A local storagemedium may be maintained, for example, on a local computing device, on alocal network, or on a resource such as a server within or connected toa local network. A remote storage medium may be maintained in the cloud,or at any other location other than a local network. In someembodiments, accessing the stored deck may include retrieving the deckfrom a web browser cache. Additionally or alternatively, accessing thestored deck may include accessing a live data stream of the stored deckfrom a remote source. In some embodiments, accessing the stored deck mayinclude logging into an account having a permission to access the deck.For example, accessing the stored deck may be achieved by interactingwith an indication associated with the stored deck, such as an icon orfile name, which may cause the system to retrieve (e.g., from a storagemedium) a particular electronic document associated with the indication.A stored deck of presentation slides, as discussed previously above, mayinclude any software, program, digital document, or other electronicdocument used to display or present data or information on one or moredisplayed pages in at least one deck that may be stored in a repository.

For example, a deck may be stored in repository 230-1 as shown in FIG.2. Repository 230-1 may be configured to store software, files, or code,such as presentation slides developed using computing device 100 or userdevice 220-1. Repository 230-1 may further be accessed by computingdevice 100, user device 220-1, or other components of system 200 fordownloading, receiving, processing, editing, or viewing, thepresentation slides. Repository 230-1 may be any suitable combination ofdata storage devices, which may optionally include any type orcombination of slave databases, load balancers, dummy servers,firewalls, back-up databases, and/or any other desired databasecomponents. In some embodiments, repository 230-1 may be employed as acloud service, such as a Software as a Service (SaaS) system, a Platformas a Service (PaaS), or Infrastructure as a Service (IaaS) system. Forexample, repository 230-1 may be based on infrastructure of services ofAmazon Web Services™ (AWS), Microsoft Azure™, Google Cloud Platform™,Cisco Metapod™, Joyent™, vmWare™, or other cloud computing providers.Repository 230-1 may include other commercial file sharing services,such as Dropbox™, Google Docs™, or iCloud™. In some embodiments,repository 230-1 may be a remote storage location, such as a networkdrive or server in communication with network 210. In other embodimentsrepository 230-1 may also be a local storage device, such as localmemory of one or more computing devices (e.g., computing device 100) ina distributed computing environment.

Some disclosed embodiments may include populating a first window, asecond window, and a third window with slides of a deck. Populating awindow may include receiving instructions for retrieving data from arepository to present the data in a rendered display of a window on ascreen, where the window may display information corresponding to theretrieved data. For example, populating a window may require a processorto perform a lookup in a repository for the data and information thatwill fill the rendered window on a screen. Populating a window withslides in a deck may include filling a window (e.g., the first window,the second window, and the third window) with retrieved data associatedwith a deck of slides and render the corresponding informationassociated with the deck in the window. For example, a slide deck may bestored in memory or a repository, and a processor may be configured toretrieve the information and display the information retrieved in thefirst window, the second window, and/or the third window.

Some disclosed embodiments may include receiving a selection of aparticular slide having a current version displayed in the second windowand a former version displayed in the third window. Receiving aselection may include the system accepting a user input from a computingdevice associated with a user that indicates instructions to make anelection or selection. The user input may be transmitted over a networkto a repository where the stored deck of presentation slides may bestored. A selection may include any action taken to elect, pick,designate, or otherwise choose a particular slide. A selection mayinvolve an input from a user input device (e.g., a mouse, a keyboard,touchpad, VR/AR device, or any other electrical or electromechanicaldevice from which signals may be provided) or non-user input (e.g., asensor reading, an event listener detection, or other automaticcomputerized sensing of changed circumstances). For example, a selectionmay be a mouse click, a mouseover, a highlight, a hover, a touch on atouch sensitive surface, a keystroke, a movement in a virtual interface,or any other action indicating a choice of a particular slide. Forexample, a selection may be using a mouse to click a particular slide.Additionally or alternatively, a selection may require an additionalclick of an activatable element, such as a button. A particular slidemay refer to any single, specific, unique, or distinct slide. Forexample, a particular slide may be one slide selected from a slide deck.A current version of a slide may include any existing, recent, orpresent form of a particular slide in a deck. For example, the currentversion of a slide may be the most recent form of the slide that wassaved to a repository. Additionally or alternatively, the currentversion of a slide may be the most recent form of the slide that is openand displayed on a user device. A current version displayed in thesecond window may include presenting the current version of a particularslide in a rendered second window. For example, the system may outputone or more signals configured to result in the data and informationassociated with the current version to display in the second window on ascreen of a user device. A former version of a slide may include anyprevious, earlier, past, historical, prior, or other form of the slideat a time before the present time. For example, a prior version of theslide may be recorded, saved, and/or stored in a repository withmetadata associating it as a former version of the particular slide. Aformer version displayed in the third window may include presenting theformer version of the slide in the third window. For example a processormay retrieve from a repository the former version of the particularslide and present it in the third window.

Some disclosed embodiments may include receiving a first selection of aparticular slide in a second window, and upon receipt of the firstselection, cause a rendition of the particular slide to appear in afirst window. Further, at least one processor may be configured toreceive a second selection of the particular slide in a third window;and upon receipt of the second selection, cause a rendition of theparticular slide to appear in the first window. Receiving a selection,as discussed previously above, may include the system accepting a userinput from a computing device associated with a user that indicatesinstructions to make a selection. Receiving a first selection of aparticular slide in a second window may include, for example, a userinput (e.g., a mouse click) indicating an election of a particular sliderendered visually in the second window. A user may select any slide inthe second window. For example, a user may select any slide in asequence of slides in a deck, such as the first slide in a deck, and/orthe last slide in a deck. Receiving a second selection of a particularslide in the third window may include a user input indicating anelection of a slide rendered visually in the third window. A user mayselect any slide in the third window. For example, a user may select anyof the historical versions of the particular slide appearing in thethird window. Causing a rendition of a particular slide may includeoutputting a signal resulting in a display of data and informationassociated with the particular slide in a window on a display device.For example, at least one processor may perform a lookup of theparticular slide in a repository, retrieve the data associated with theparticular slide, and output signals to cause the data of the particularslide to be visually displayed in a window with information associatedwith the particular slide. Causing a rendition of a particular slide toappear in the first window may include showing, presenting, outputting,rendering, mirroring, or otherwise displaying the selected particularslide in the first window. For example, a user may select a slide in thesecond window, and the system may be configured to display the selectedslide in the first window.

For example, FIG. 13A to FIG. 13C may represent a stored deck ofpresentation slides presented on a display device. In FIG. 13A, a usermay select (e.g., via a mouse click or any other interaction) aparticular slide 1308A from the second window 1304A (e.g., the currentgraphical slide sequence), which may cause the particular slide 1308A toappear in the first window 1302A, Next, as shown in FIG. 13B, a user mayselect a particular slide 1302B in the third window 1306A (e.g., ahistorical graphical slide sequence), which may cause the particularslide 1302B to appear in the first window 1302A.

Some disclosed embodiments may include receiving a drag of a particularslide from the third window into the second window, to therebyreincorporate an earlier version of the particular slide from the formerversion into the current sequence of slides in the second window, wherethe at least on processor may be further configured to store in atimeline repository, a first record of the drag. Receiving a drag mayinclude the system accepting a user input from a computing deviceassociated with a user that indicates instructions to make an electionof a data object in a rendered display and reposition the visualrepresentation of the data object to a different location in therendered display. The user input may be transmitted over a network to arepository where the stored deck of presentation slides may be stored. Adrag may refer to an election of a visual representation of a dataobject (e.g., clicking on a particular slide) and repositioning thevisual representation of the data object to a different location in ascreen. For example, a drag may include pressing a mouse button down andmoving the mouse while holding the button to send instructions to theprocessor to reposition a data object in a rendered display ofinformation. Alternatively, a drag may refer to a mouse click in a firstlocation on a display device and a second mouse click in a secondlocation on the display device to indicate an intent to cause a drag ofa data object. For example, a drag may involve electing a particularslide rendered in a third window and repositioning the particular slideto a second window. Dragging a particular slide between differentwindows may include a seamless visualization of repositioning theparticular slide from one window to another, or may involve are-rendering of the display of information in a particular slide tosimply appear in another window. Reincorporating an earlier version ofthe particular slide from the former version into the current sequenceof slides in the second window may include receiving instructions toretrieve information associated with a previously recorded version of aslide and replacing a current version of the slide in memory to adoptthe previously recorded version of the slide into the current version ofa presentation file. Reincorporating an earlier version may involveoutputting one or more signals configured to result in the rendering ofthe earlier version of the particular slide in the second window. Forexample, the earlier version may replace the current version displayedin the second window. Similarly, for example, the earlier version of theparticular slide may be stored with a current sequence of slides in thedeck so a former version of the particular slide may appear in thecurrent sequence of slides in the deck, and the replaced version maythen be stored in a repository as a historical version of the slide(e.g., the replaced version may become a new “earlier” version of theslide sequence after it is replaced). A timeline repository may includeany memory, repository, or other storage medium that may contain data orinformation and or commands, operations, or instructions capable ofbeing carried out by at least one processor. For example, historicalversions of a slide may be stored in a timeline repository. Storing in atimeline repository, a record of the drag may include saving, recording,keeping, maintaining, or preserving the first record of the drag inmemory or repository (e.g., data structure). For example, the timelinerepository may record each drag so each historical version of aparticular slide may be retrieved and rendered to appear in the thirdwindow in chronological order according to a timestamp that may bestored with each record of each drag.

Upon dragging, some disclosed embodiments may include moving anassociated slide from a second window to a third window and storing in atimeline repository a second record of the moving. An associated slidefrom a second window may include any slide in the second window that ismoved, rearranged, modified, corrected, replaced, or otherwise changeddue to the dragging. Moving an associated slide from a second window toa third window may include causing the rendition of the associated slidein the third window, as discussed previously above. For example, a slidein the second window may be replaced by the dragging of a historicalversion of the slide from the third window, and the system may beconfigured to cause the associated replaced slide to appear in the thirdwindow. As a result of moving the associated slide from the secondwindow to the third window (e.g., a drag) the processor may, in responseto detecting the moving, store in the timeline repository a secondrecord of the moving.

In some disclosed embodiments, at least one processor may be configuredto present a slider extending between a second window and a thirdwindow, to enable sequential sets of changes to be displayed as theslider is dragged from a location proximate the third windowrepresenting an earliest slide version to a location proximate thesecond window representing a latest slide version. Further disclosedembodiments may include receiving a selection of a slide portion from anearlier version for incorporation into a current version, Presenting aslider extending between the second window and the third window mayinclude causing a display of an interactable element between windows forinteracting with displayed information between windows, such as in theform of a slider. A slider may be part of a visual interface thatdisplays multiple previous versions corresponding to a particular slide,where the slide may be an activatable element that enables a user toview the previous versions of the particular slide. For example, theslider extending between the second window and the third window mayinclude causing multiple previous versions of the particular slide to berendered in a displayed interface. Enabling sequential sets of changesto be displayed may including receiving instructions to retrievehistorical alteration data to a particular slide and causing thehistorical alteration data to be rendered on a screen in a chronologicalorder. Sequential sets of changes may include edits made previously, inthe past, prior to, or otherwise made at a time before the present timein an order of when the changes were made in a particular logical order,such as in a chronological manner. For example, changes may be stored ina repository with metadata associated with an instance in time such thatthe at least one processor may determine the order changes were made toa particular slide and display, via a display device, the changes in anorder. A location proximate a window may include any place or positionthat is near, next to, adjacent, or otherwise close to a window. Awindow, as discussed above, may represent a particular version of aslide in time, with one window rendering information from an earliestslide version and another window rendering information from a latestslide version. For example, the processor may lookup historical dataassociated with a particular slide in a repository and cause a displayof a progression of changes made over time to the slide based onmetadata identifying a timestamp associated with different historicalversions of the slide, such as displaying the earliest versions of aslide (e.g., earliest timestamp) near the third window and the mostrecent changes (e.g., latest timestamp) appearing near the secondwindow. This may allow, for example, a user to identify the edits madeto a particular slide over time. A slide portion may include any subset,piece, segment, section, or other part of information displayed in avisually rendered slide. Receiving a selection of a slide portion froman earlier version, as discussed above, may include choosing, picking,or otherwise selecting a portion of a slide from an earlier version andincorporating it into a current version. For incorporation into acurrent version may refer to accessing the current version data andreplacing it with data from an earlier version of the particular slide.The data associated with the replaced version may be stored in therepository associated with the particular slide as a historical versionof the particular slide. For example, a user may select a part of ahistorical version of the particular slide (e.g., a single sentence in aparagraph), and instead of reincorporating the entire slide, asdiscussed above, the system may be configured to reincorporate the partof the historical version chosen (e.g., the single sentence in theparagraph). For example, the title of a particular slide may change overtime, and the information presented on the slide may also change. Thesystem may allow a user to keep the information presented on the currentslide but reincorporate the previous title. For example, a historicalversion of a particular slide may be stored in a repository and the dataassociated with the title may be different from the title of the currentslide. In response to a user selection of the title from the historicalversion, the system may access the data associated with the title of thecurrent version and replace it with the title of the historical version.The version of the slide with the replaced title (e.g., the currentversion before the user selection) may then be stored in a repository asa new historical version of the particular slide.

Some disclosed embodiments may include displaying a timeline slider inassociation with a particular slide, the timeline slider enablingviewing of a sequence of changes that occurred over time to theparticular slide, and where at least one processor may additionally beconfigured to receive an input via the timeline slider to cause adisplay of an editing rollback of the particular slide. Displaying atimeline slider may include rendering an interactive display of aninterface that may present historical information associated with aparticular slide in a sequential order (e.g., chronological). Forexample, historical versions of a particular slide may be displayedwhich may require the at least one processor to perform a lookup of thehistorical versions of a particular slide in storage or a repository,and then implement and present the historical versions with the timeslider. Each historical version of a particular slide may includemetadata associated with the version allowing the at least one processorto identify the version and distinguish it from other versions of theparticular slide. A timeline slider in association with a particularslide may include one or more interactable visual elements, such as aslider with markers, enabling a user to change between displays ofdifferent previous versions of the particular slide. For example, a usermay click a marker on the timeline slider and the marker may allow theuser to view a version of the particular slide associated with thatmarker. A user may then click a different marker on the timeline sliderwhich may cause the display of a different version of the particularslide. Enabling viewing of a sequence of changes that occurred over timeto the particular slide may include causing a display of historicalinformation associated with a particular slide such that an authorizeduser may view and interact with the historical alterations made to theparticular slide in a timeframe. For example, the timeline slider may bepresented to enable a user to view previous versions or forms of aparticular slide and interact with these previous versions of theparticular slide for incorporating into an electronic file. Receiving aninput may include detecting an instruction from an associated computingdevice of a user or account that indicates an intent for choosing,picking, deciding, appointing, or otherwise selecting (e.g., by a mouseclick, gesture, cursor movement, or any other action by a user) aspecific action, such as selecting data in memory to adopt into acurrent version of an electronic document. For example, receiving aninput may be a data input from a computer device. Receiving an input mayinclude any signal or indication that meets a threshold for carrying outinstructions for presenting an editing rollback display, such asperforming a look up of data or information stored in a repositoryassociated with the particular slide. Causing a display of an editingrollback of the particular slide may include rendering a presentation ofa historical version of a particular slide in response to receiving aninput by a user to view historical information associated with theparticular slide. An editing rollback of a particular slide may includea displayed preview of a previous version of the particular slide in amanner that returns a current display of the particular slide to theprevious version. For example, the system may receive an input via thetimeline slider, such as selecting a version of the particular slide,and in response to the selection, the system may perform a lookup of thedata and information stored in a repository associated with the selectedversion. As a result of the lookup, the processor may retrievehistorical data and present it in a display as an editing rollback forthat particular slide in a manner enabling a user to interact with thehistorical data for further manipulation or adoption.

For example, FIG. 14 illustrates a timeline slider 1400. A user mayinteract with the timeline slider 1400 by, for example, dragging avisual icon 1402 (e.g., the rocket ship) or by clicking on a marker1404. Changing between different markers may allow a user to view asequence of changes made over time to a particular slide. A user mayalso interact with the timeline slider 1400 to provide an input to theprocessor by interacting with an interactable element 1406 that may sendinstructions to cause a display of editing rollback of the particularslide in a rendered display 1408.

During a display of an editing rollback, some disclosed embodiments mayinclude a display characteristic that differs from a displaycharacteristic that occurs during a current slide display. A displaycharacteristic may include any visual feature, trait, element,interface, attribute, or other quality of slide. A displaycharacteristic different from a display characteristic that occursduring a current slide display may include any display characteristicthat is unique, distinct, changed, individual, or otherwise not the sameas the display characteristic of the current slide display. For example,a historical version of a particular slide may not have any graphicalimages or pictures associated with the slide, while the current slidedisplay may contain pictures. In another example, a historical versionof a particular slide may have a display characteristic where the textis displayed with a red color while a display characteristic of thecurrent version of the particular slide may be displayed with a blackcolor.

FIG. 15 illustrates a block diagram of an example process 1500 fortracking on a slide-by-slide basis, edits to presentation slides. Whilethe block diagram may be described below in connection with certainimplementation embodiments presented in other figures, thoseimplementations are provided for illustrative purposes only, and are notintended to serve as a limitation on the block diagram. In someembodiments, the process 1500 may be performed by at least one processor(e.g., the processing circuitry 110 in FIG. 1) of a computing device(e.g., the computing device 100 in FIGS. 1 and 2) to perform operationsor functions described herein and may be described hereinafter withreference to FIGS. 13 to 14 by way of example. In some embodiments, someaspects of the process 1500 may be implemented as software (e.g.,program codes or instructions) that are stored in a memory (e.g., thememory portion 122 in FIG. 1) or a non-transitory computer-readablemedium. In some embodiments, some aspects of the process 1500 may beimplemented as hardware (e.g., a specific-purpose circuit). In someembodiments, the process 1500 may be implemented as a combination ofsoftware and hardware.

FIG. 15 may include process blocks 1502 to 1520:

At block 1502, the processing means may be configured to present a firstwindow defining a slide pane for displaying a slide subject to editing,consistent with some embodiment discussed above.

At block 1504, the processing means may be configured to present in asecond window a current graphical slide sequence pane, for graphicallydisplaying a current sequence of slides in the deck, as discussedpreviously in the disclosure above.

At block 1506, the processing means may be configured to present in athird window an historical graphical slide sequence pane for graphicallypresenting a former sequence of slides in the deck, as discussedpreviously above.

At block 1508, the processing means may be configured to access a storeddeck of presentation slides, as discussed previously.

At block 1510, the processing means may be configured to populate thefirst window, the second window, and the third window with slides of thedeck, as discussed previously above.

At block 1512, the processing means may be configured to receive aselection of a particular slide having a current version displayed inthe second window and a former version displayed in the third window, asdiscussed previously above.

At block 1514, the processing means may include receiving a firstselection of the particular slide in the second window, as discussedabove.

At block 1516 the processing means may be further configured to cause arendition of the particular slide to appear in the first window,consistent with the earlier disclosure.

At block 1518, the processing means may be further configured receive asecond selection of the particular slide in the third window, asdiscussed previously in the disclosure above.

At block 1520 the processing means may be further configured cause arendition of the particular slide to appear in the first window,consistent with the earlier disclosure.

Unless otherwise defined, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art. The materials, methods, and examples provided herein areillustrative only and not intended to be limiting.

Implementation of the method and system of the present disclosure mayinvolve performing or completing certain selected tasks or stepsmanually, automatically, or a combination thereof. Moreover, accordingto actual instrumentation and equipment of preferred embodiments of themethod and system of the present disclosure, several selected steps maybe implemented by hardware (HW) or by software (SW) on any operatingsystem of any firmware, or by a combination thereof. For example, ashardware, selected steps of the disclosure could be implemented as achip or a circuit. As software or algorithm, selected steps of thedisclosure could be implemented as a plurality of software instructionsbeing executed by a computer using any suitable operating system. In anycase, selected steps of the method and system of the disclosure could bedescribed as being performed by a data processor, such as a computingdevice for executing a plurality of instructions.

As used herein, the terms “machine-readable medium” “computer-readablemedium” refers to any computer program product, apparatus and/or device(e.g., magnetic discs, optical disks, memory, Programmable Logic Devices(PLDs)) used to provide machine instructions and/or data to aprogrammable processor, including a machine-readable medium thatreceives machine instructions as a machine-readable signal. The term“machine-readable signal” refers to any signal used to provide machineinstructions and/or data to a programmable processor.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

Although the present disclosure is described with regard to a “computingdevice”, a “computer” or “mobile device”, it should be noted thatoptionally any device featuring a data processor and the ability toexecute one or more instructions may be described as a computing device,including but not limited to any type of personal computer (PC), aserver, a distributed server, a virtual server, a cloud computingplatform, a cellular telephone, an IP telephone, a smartphone, a smartwatch or a PDA (personal digital assistant). Any two or more of suchdevices in communication with each other may optionally comprise a“network” or a “computer network”.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(a LED (light-emitting diode), or OLED (organic LED), or LCD (liquidcrystal display) monitor/screen) for displaying information to the userand a keyboard and a pointing device (e.g., a mouse or a trackball) bywhich the user can provide input to the computer. Other kinds of devicescan be used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback (e.g.,visual feedback, auditory feedback, or tactile feedback); and input fromthe user can be received in any form, including acoustic, speech, ortactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

It should be appreciated that the above described methods and apparatusmay be varied in many ways, including omitting or adding steps, changingthe order of steps and the type of devices used. It should beappreciated that different features may be combined in different ways.In particular, not all the features shown above in a particularembodiment or implementation are necessary in every embodiment orimplementation of the invention. Further combinations of the abovefeatures and implementations are also considered to be within the scopeof some embodiments or implementations of the invention.

While certain features of the described implementations have beenillustrated as described herein, many modifications, substitutions,changes and equivalents will now occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the scope of theimplementations. It should be understood that they have been presentedby way of example only, not limitation, and various changes in form anddetails may be made. Any portion of the apparatus and/or methodsdescribed herein may be combined in any combination, except mutuallyexclusive combinations. The implementations described herein can includevarious combinations and/or sub-combinations of the functions,components and/or features of the different implementations described.

Disclosed embodiments may include anyone of the following bullet-pointedfeatures alone or in combination with one or more other bullet-pointedfeatures, whether implemented as a method, by at least one processor,and/or stored as executable instructions on non-transitorycomputer-readable media:

-   -   accessing a collaborative electronic document;    -   linking a first entity and a second entity to form a first        collaborative group;    -   linking a third entity and a fourth entity to form a second        collaborative group;    -   receiving a first alteration by the first entity to the        collaborative electronic document;    -   tagging the first alteration by the first entity with a first        collaborative group indicator;    -   receiving a second alteration to the collaborative electronic        document by the second entity;    -   tagging the second alteration by the second entity with the        first collaborative group indicator;    -   receiving a third alteration to the collaborative electronic        document by the third entity;    -   tagging the third alteration by the third entity with a second        collaborative group indicator,    -   receiving a fourth alteration from the fourth entity to the        collaborative electronic document;    -   tagging the fourth alteration by the fourth entity with the        second collaborative group indicator;    -   rendering a display of the collaborative electronic document;    -   wherein the rendered display includes presenting the first        collaborative group indicator in association with the first        alteration and the second alteration;    -   wherein the rendered display includes the second collaborative        group indicator displayed in association with the third        alteration and the fourth alteration;    -   wherein the first collaborative group includes a plurality of        first additional entities linked to the first and second        entities;    -   wherein the second collaborative group includes a plurality of        second additional entities linked to the third and fourth        entities;    -   wherein the displayed first collaborative group indicator in        association with the first alteration and the second alteration        includes a first instance of the first collaborative group        indicator displayed in association with the first alteration and        a second instance of the first collaborative group indicator        displayed in association with the second alteration;    -   wherein the third alteration and the fourth alteration includes        a first instance of the second collaborative group indicator        displayed in association with the third alteration and a second        instance of the second collaborative group indicator displayed        in association with the fourth alteration;    -   preventing the second collaborative group from making edits to        the first alteration and the second alteration;    -   receiving an attempt by a fifth entity to change the first        alteration;    -   accessing permissions settings;    -   determining whether the fifth entity possesses a permission        enabling change of the first alteration;    -   upon determination of a change-enabling permission, applying the        change to the first alteration;    -   wherein the determination that the fifth entity possesses the        permission is based on a determination that the fifth entity is        associated with the first collaborative group;    -   recognizing the fifth entity as a member of a third        collaborative group with permission to change alterations of the        first collaborative group    -   permitting the change to the first alteration;    -   tagging the change with a third collaborative group indicator;    -   receiving an attempt by a sixth entity to change the first        alteration;    -   accessing permissions settings;    -   determining whether that the six entity lacks permission        enabling change of the first alteration;    -   generating a duplicate version of the collaborative electronic        document in which the sixth entity is permitted to change the        first alteration;    -   accessing the electronic document, having an original form;    -   recording at a first time, first edits to a specific portion of        the electronic document;    -   recording at a second time, second edits to the specific portion        of the electronic document;    -   recording at a third time, third edits to the specific portion        of the electronic document;    -   receiving at a fourth time, a selection of the specific portion;    -   in response to the selection, rendering a historical interface        enabling viewing of an original form of the selection, the first        edits, the second edits, and the third edits;    -   receiving an election of one of the original form of the        electronic document, the first edits, the second edits, and the        third edits;    -   upon receipt of the election, presenting a rolled-back display        reflecting edits made to the specific portion of the electronic        document, the rolled-back display corresponding to a past time        associated with the election;    -   wherein the historical interface includes an interactive        timeline enabling rollback of edits to markers on the timeline        denotating the original form of the selection, the first edits,        the second edits, and the third edits;    -   wherein the first edits were made by a first entity, the second        edits were made by a second entity and the third edits were made        by a third entity, and wherein the markers enable identification        of a particular entity associated with a particular edit;    -   wherein the markers indicate an identity of an associated entity        responsible for an associated edit;    -   wherein the first edits, the second and the third edits are each        associated with a common entity;    -   applying a time interval to document edits and wherein selection        of a particular marker causes presentation of changes that        occurred during the time interval;    -   wherein the time interval is user-definable;    -   wherein the historical interface is configured to simultaneously        display the first edit, the second edit, and the third edit;    -   co-displaying the timeline in a vicinity of the specific portion        of the electronic document;    -   presenting a first window defining a slide pane for displaying a        slide subject to editing;    -   presenting in a second window a current graphical slide sequence        pane, for graphically displaying a current sequence of slides in        the deck;    -   presenting in a third window a historical graphical slide        sequence pane for graphically presenting a former sequence of        slides in the deck;    -   accessing a stored deck of presentation slides;    -   populating the first window, the second window, and the third        window with slides of the deck;    -   receiving a selection of a particular slide having a current        version displayed in the second window and a former version        displayed in the third window;    -   receiving a first selection of the particular slide in the        second window;    -   upon receipt of the first selection, causing a rendition of the        particular slide to appear in the first window;    -   receiving a second selection of the particular slide in the        third window;    -   upon receipt of the second selection, causing a rendition of the        particular slide to appear in the first window;    -   receiving a drag of the particular slide from the third window        into the second window, to thereby reincorporate an earlier        version of the particular slide from the former version into the        current sequence of slides in the second window;    -   storing in a timeline repository, a first record of the drag;    -   moving an associated slide from the second window to the third        window and storing in the timeline repository a second record of        the moving;    -   displaying a timeline slider in association with the particular        slide, the timeline slider enabling viewing of a sequence of        changes that occurred over time to the particular slide;    -   receiving an input via the timeline slider to cause a display of        an editing rollback of the particular slide;    -   wherein during display of an editing rollback, a display        characteristic differs from a display characteristic that occurs        during a current slide display;    -   presenting a slider extending between the second window and the        third window, to enable sequential sets of changes to be        displayed as the slider is dragged from a location proximate the        third window representing an earliest slide version to a        location proximate the second window representing a latest slide        version; and    -   receiving a selection of a slide portion from an earlier version        for incorporation into a current version.

Systems and methods disclosed herein involve unconventional improvementsover conventional approaches. Descriptions of the disclosed embodimentsare not exhaustive and are not limited to the precise forms orembodiments disclosed. Modifications and adaptations of the embodimentswill be apparent from consideration of the specification and practice ofthe disclosed embodiments. Additionally, the disclosed embodiments arenot limited to the examples discussed herein.

The foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations of theembodiments will be apparent from consideration of the specification andpractice of the disclosed embodiments. For example, the describedimplementations include hardware and software, but systems and methodsconsistent with the present disclosure may be implemented as hardwarealone.

It is appreciated that the above described embodiments can beimplemented by hardware, or software (program codes), or a combinationof hardware and software. If implemented by software, it can be storedin the above-described computer-readable media. The software, whenexecuted by the processor can perform the disclosed methods. Thecomputing units and other functional units described in the presentdisclosure can be implemented by hardware, or software, or a combinationof hardware and software. One of ordinary skill in the art will alsounderstand that multiple ones of the above described modules/units canbe combined as one module or unit, and each of the above describedmodules/units can be further divided into a plurality of sub-modules orsub-units.

The block diagrams in the figures illustrate the architecture,functionality, and operation of possible implementations of systems,methods, and computer hardware or software products according to variousexample embodiments of the present disclosure. In this regard, eachblock in a flowchart or block diagram may represent a module, segment,or portion of code, which includes one or more executable instructionsfor implementing the specified logical functions. It should beunderstood that in some alternative implementations, functions indicatedin a block may occur out of order noted in the figures. For example, twoblocks shown in succession may be executed or implemented substantiallyconcurrently, or two blocks may sometimes be executed in reverse order,depending upon the functionality involved. Some blocks may also beomitted. It should also be understood that each block of the blockdiagrams, and combination of the blocks, may be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or by combinations of special purpose hardware and computerinstructions.

In the foregoing specification, embodiments have been described withreference to numerous specific details that can vary from implementationto implementation. Certain adaptations and modifications of thedescribed embodiments can be made. Other embodiments can be apparent tothose skilled in the art from consideration of the specification andpractice of the invention disclosed herein. It is intended that thespecification and examples be considered as example only, with a truescope and spirit of the invention being indicated by the followingclaims. It is also intended that the sequence of steps shown in figuresare only for illustrative purposes and are not intended to be limited toany particular sequence of steps. As such, those skilled in the art canappreciate that these steps can be performed in a different order whileimplementing the same method.

It will be appreciated that the embodiments of the present disclosureare not limited to the exact construction that has been described aboveand illustrated in the accompanying drawings, and that variousmodifications and changes may be made without departing from the scopethereof.

Other embodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the disclosedembodiments disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the disclosed embodiments being indicated by the following claims.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. One or more of such software sections or modulescan be integrated into a computer system, non-transitory computerreadable media, or existing software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication. These examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as exemplary only, with a true scope and spirit beingindicated by the following claims and their full scope of equivalents.

What is claimed is:
 1. A system for tracking on a slide-by-slide basis,edits to presentation slides, the system comprising: at least oneprocessor configured to: present a first window defining a slide panefor displaying a slide subject to editing; present in a second window acurrent graphical slide sequence pane, for graphically displaying acurrent sequence of slides in the deck; present in a third window ahistorical graphical slide sequence pane for graphically presenting aformer sequence of slides in the deck; access a stored deck ofpresentation slides; populate the first window, the second window, andthe third window with slides of the stored deck; receive a selection ofa particular slide having a current version displayed in the secondwindow and a former version displayed in the third window; receive afirst selection of the particular slide in the second window; uponreceipt of the first selection, cause a rendition of the particularslide having the current version to appear in the first window; receivea second selection of the particular slide in the third window; uponreceipt of the second selection, cause a rendition of the particularslide having the former version to appear in the first window; receive adrag of the particular slide from the third window into the secondwindow, to thereby reincorporate an earlier version of the particularslide from the former version into the current sequence of slides in thesecond window, and store in a timeline repository, a first record of thedrag; and in response to the drag, move an associated slide from thesecond window to the third window and storing in the timeline repositorya second record of the moving.
 2. The system of claim 1, wherein the atleast one processor is further configured to display a timeline sliderin association with the particular slide, the timeline slider enablingviewing of a sequence of changes that occurred over time to theparticular slide, and wherein the at least one processor is furtherconfigured to receive an input via the timeline slider to cause adisplay of an editing rollback of the particular slide.
 3. The system ofclaim 2, wherein during display of an editing rollback, a displaycharacteristic differs from a display characteristic that occurs duringa current slide display.
 4. The system of claim 1, wherein the at leastone processor is further configured to present a slider extendingbetween the second window and the third window, to enable sequentialsets of changes to be displayed as the slider is dragged from a locationproximate the third window representing an earliest slide version to alocation proximate the second window representing a latest slideversion.
 5. The system of claim 4, wherein the at least one processor isfurther configured to receive a selection of a slide portion from anearlier version for incorporation into a current version.
 6. Anon-transitory computer readable medium including instructions that,when executed by at least one processor, cause the at least oneprocessor to perform operations for tracking on a slide-by-slide basis,edits to presentation slides, the operations comprising: presenting afirst window defining a slide pane for displaying a slide subject toediting; presenting in a second window a current graphical slidesequence pane, for graphically displaying a current sequence of slidesin the deck; presenting in a third window an historical graphical slidesequence pane for graphically presenting a former sequence of slides inthe deck; accessing a stored deck of presentation slides; populating thefirst window, the second window, and the third window with slides of thestored deck; receiving a selection of a particular slide having acurrent version displayed in the second window and a former versiondisplayed in the third window; receiving a first selection of theparticular slide in the second window; upon receipt of the firstselection, causing a rendition of the particular slide having thecurrent version to appear in the first window; receiving a secondselection of the particular slide in the third window; upon receipt ofthe second selection, causing a rendition of the particular slide havingthe former version to appear in the first window; receiving a drag ofthe particular slide from the third window into the second window, tothereby reincorporate an earlier version of the particular slide fromthe former version into the current sequence of slides in the secondwindow, and storing in a timeline repository, a first record of thedrag; and in response to the drag, moving an associated slide from thesecond window to the third window and storing in the timeline repositorya second record of the moving.
 7. The non-transitory computer readablemedium of claim 6, wherein the operations further include displaying atimeline slider in association with the particular slide, the timelineslider enabling viewing of a sequence of changes that occurred over timeto the particular slide, and wherein the operations additionally includereceiving an input via the timeline slider to cause a display of anediting rollback of the particular slide.
 8. The non-transitory computerreadable medium of claim 7, wherein during display of an editingrollback, a display characteristic differs from a display characteristicthat occurs during a current slide display.
 9. The non-transitorycomputer readable medium of claim 6, wherein the operations furthercomprise presenting a slider extending between the second window and thethird window, to enable sequential sets of changes to be displayed asthe slider is dragged from a location proximate the third windowrepresenting an earliest slide version to a location proximate thesecond window representing a latest slide version.
 10. Thenon-transitory computer readable medium of claim 9, wherein theoperations further include receiving a selection of a slide portion froman earlier version for incorporation into a current version.